final String sessionId;
            if (searchLog.getUserSessionId() != null) {
                sessionId = searchLog.getUserSessionId();
            } else if (Constants.SEARCH_LOG_ACCESS_TYPE_WEB.equals(searchLog.getAccessType())) {
                sessionId = searchLog.getClientIp();
            } else {
                sessionId = searchLog.getClientIp() + '_' + searchLog.getSearchWord();
            }

            bhv.selectCursor(cb -> {
                cb.query().matchAll();
                cb.query().addOrderBy_RequestedAt_Asc();
            }, new LogEntityRowHandler<SearchLog>() {
                @Override
                public void handle(final SearchLog entity) {
                    final StringBuilder buf = new StringBuilder();
                    buf.append('{');

    public static final String SUGGEST_SEARCH_LOG_PROPERTY = "suggest.searchlog";

    public static final String SUGGEST_DOCUMENTS_PROPERTY = "suggest.document";

    public static final String PURGE_SUGGEST_SEARCH_LOG_DAY_PROPERTY = "purge.suggest.searchlog.day";

    public static final String LTR_MODEL_NAME_PROPERTY = "ltr.model.name";

page.thumbnail.purge.max.fetch.size=100
page.score.booster.max.fetch.size=1000
page.searchlog.max.fetch.size=10000

page.searchlist.track.total.hits=true

# search page
paging.search.page.start=0
paging.search.page.size=10
paging.search.page.max.size=100

searchlog.agg.shard.size=-1
searchlog.request.headers=
searchlog.process.batch_size=100

thumbnail.html.image.min.width=100

    /** The key of the configuration. e.g. -1 */
    String SEARCHLOG_AGG_SHARD_SIZE = "searchlog.agg.shard.size";

    /** The key of the configuration. e.g.  */
    String SEARCHLOG_REQUEST_HEADERS = "searchlog.request.headers";

    /** The key of the configuration. e.g. 100 */
    String SEARCHLOG_PROCESS_batch_size = "searchlog.process.batch_size";

    /** The key of the configuration. e.g. 100 */

* Bridging this into an OSGi system: if this could be done then we can basically take over p2

TODO

- dealing with processing of input and adapting GAVs before searching i.e. plugin groups in Maven and default searching
- how to deal with resolution from different places like local/remote/workspace
- how to incorporate the metadata processor to start with
- create a hook to programmatically configure the test

<font color="#3465A4">INFO    </font> Resolved absolute path <font color="#75507B">/home/user/code/awesomeapp/</font><font color="#AD7FA8">main.py</font>
<font color="#3465A4">INFO    </font> Searching for package file structure from directories with <font color="#3465A4">__init__.py</font> files
<font color="#3465A4">INFO    </font> Importing from <font color="#75507B">/home/user/code/</font><font color="#AD7FA8">awesomeapp</font>

        return methods;
    }

    /**
     * Recursively finds a match for each method, starting with the class, and then
     * searching the superclass and interfaces.
     *
     * @param clazz       Class to check
     * @param methodInfos array of methods we are searching to match
     * @param upcastCount current number of methods we have matched
     * @return count of matched methods
     */

                        writer.flush();
                    }
                });
            }
            final String name = id.substring(0, id.length() - NDJSON_EXTENTION.length());
            if ("search_log".equals(name)) {
                return writeNdjsonResponse(id, getSearchLogNdjsonWriteCall());
            }
            if ("user_info".equals(name)) {

		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_log.favorite_log/favorite_log"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_log.search_log/search_log"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_log.user_info/user_info"</arg>
		</postConstruct>
	</component>