search-engine | 基于elasticsearch | Application Framework library

I'm trying to use Sentence Transformers and Haystack for document retrieval, focusing on searching documents on other metadata beside document text.

I'm using a dataset of academic publication titles, and I've appended a fake publication year (which I want to use as a search term). From reading around I've combined the columns and just added a separator between the title and publication year, and included the column titles since I thought maybe this could add context. An example input looks like:

title Sparsity-certifying Graph Decompositions [SEP] published year 1980

I have a document store and method of retrieving here, based on this:

I'm new to CSS and I wanted to add some margin-right to the placeholder of an input:

I'm trying to bind a list of objects to my entity class using @ConfigurationProperties annotation. Spring Boot framework seems to ignore that annotation, and it literally does nothing.

Here is my application.yml properties file:

I'm testing a controller for a Spring Boot application. I want to map a resource to a path, which should be a part of my API. My controller is pretty specific about path:

I did a react project for my bootcamp, and just pulled it down from my github again, after running npm i and npm run-script build I am getting a white screen with 3 errors in the console. 2 of the errors are Uncaught SyntaxError: Unexpected token '<' and the other is Manifest: Line: 1, column: 1, Syntax error.

These errors are not showing on the deployed version, and I am wondering how to get rid of them so I can start working on it on my local host.

Repo: https://github.com/childishmartino/Book-Search-Engine

My initial program was intended to insert data into my database. I have 4 tables, where data is inserted, and for optimization's sake, I'm doing that in a seperate thread, because entities are created asynchronous. I'm adding entities to a queue with consume method.

I am working on my diploma exam with topic of Full-Text Search in Apache SOLR. Within the introduction, I should elaborate what are the purpose and advantages of Apache SOLR, i.e. why would one opt for Full-Text Search engine like SOLR instead of MySQL, for instance. Using literature like "SOLR in action (2013)" one would say it's rather easy to determine when to use SOLR, ElasticSearch or something else, instead of MySQL - for that era. There is also this great question from 2010 on SO: Comparison of full text search engine - Lucene, Sphinx, Postgresql, MySQL?. Alas, as great as it was around 2010, answers now seem painfully obsolete. E.g. "MySQL MyISAM table type supports Full-Text Search, but InnoDB does not". Several years after this InnoDB also added Full-Text Search support. Now, there are some articles that manage to shed some light on this, like https://lucidworks.com/post/full-text-search-engines-vs-dbms/ which states that advantages of Full-Text Search systems are

search speed, variety of indexing and querying options, ranking and relevancy capabilities...

Yet, there are lot of other articles stating things like

MySQL Full-Text Search will now fit your needs in 80% of cases

etc, and it seems that over past 10 years MySql, MongoDB, PostgreSQL and other relational database Full-Text Search capability increased dramatically.

Yet, graph on https://db-engines.com/en/ranking_trend/system/Elasticsearch%3BMySQL%3BSolr shows that Full-Text Search engines are not losing popularity, but their usage is growing, and even SOLR that was losing pace steadily, now seems to be waking up.

So, there must be something to it? Is it that:

• SOLR, Elastic, Sphinx... are still considerably faster than their relational counterparts?
• there is larger variety of options, like advanced, customizable tokenization, faceting? Maybe better languages support?
• relational databases can't handle well enough search on very large number of documents?

etc.

In short, what would make you take Apache SOLR or Elastic nowadays, instead of MySQL or other relational database with their increased Full-Text search capabilities? Why are Apache SOLR and Elastic Search still that popular when using them requires another stack of resources and administration if you already have data in your relational or NoSQL database?

So the central question is: If I have system that uses MySQL database for data storage, and I need to add full text search capabilities for one or several fields, to include fuzzy search (typos), synonyms, stemming, to handle relevancy and ranking in custom way, is it generally better to use MySQL FTS (so no need for another stack of resources and administration) or a dedicated full text search engine like Apache SOLR or Elastic search is significantly enough better at this?

Hi please anyone can help me with this list i want to separate the data into three parts, the whole data below is located at a single index of the list, such that each index of the list has a data of this kind.

So I have created a folder in VS code with an HTML, JS and CSS file, when I open it in the browser it gives me this error in the console:

script.js:21 Uncaught TypeError: Cannot set properties of null (setting 'innerHTML') at script.js:21

dateTime.innerHTML = ${day}, ${hours}:${minutes};

None of the JS appears to work on VS code, but when I copy the exact same code to code sandbox it works perfectly.

Would really appreciate it if someone could help me solve this issue.

Thanks in advance! :)

*The script tag is okey linked to the html, because if I alert("Hello") The pop up appears in the browser when using VSCode.

This is my HTML code