Could not load text adapter configs from dir 'config/data_sources/nlp'

[KonradHoeffner]

Executing docker compose up in top-deployment results in the following backend warning:

backend-1   | 2024-02-14 10:47:15.940  WARN 1 --- [nio-8080-exec-4] c.s.t.b.s.nlp.DocumentQueryService       : Could not load text adapter configs from dir 'config/data_sources/nlp'

[fmatthies]

Is this locally on your machine? This is an example of a text adapter config source:

id: Lucene Data Source
adapter: care.smith.top.top_document_query.adapter.lucene.LuceneAdapter
connection:
  url: http://localhost
  port: 9201
index:
  - test_documents
field:
  - text
batchSize: 30
replaceFields: {'text': 'content'}
graphDB:
  connection:
    url: bolt://localhost
    port: 7687
conceptGraph:
  connection:
    url: http://localhost
    port: 5000

Supposing, you don't have the services running locally, you could forward the ports from top-prod.

• elasticSearch (the main connection) runs on 9008
• graphDB runs on 7687
• conceptGraph runs on 9007

[KonradHoeffner]

Yes, this is locally on my machine when I just git clone and docker compose up. Can we include this in the docker compose setup or disable the warning otherwise?

[fmatthies]

We need to postpone this issue until @ChristophB finishes the restructuring of the backend and how we handle the whole document/concept situation. If Elasticsearch is loaded/connected to within the backend, this warning is hard/not to circumvent as spring will expect an Elasticsearch server. If we handle the whole concept/document situation as an integral part, however, we could load up the Elasticsearch server with an docker compose entry accordingly.

[ChristophB]

The changes I have implemented so far do not affect this warning. How about we reduce the log level of this message to debug?