Skip to content

Add Viglet Turing ES to Search#1287

Open
alegauss wants to merge 1 commit into
akullpp:masterfrom
alegauss:add-viglet-turing-es
Open

Add Viglet Turing ES to Search#1287
alegauss wants to merge 1 commit into
akullpp:masterfrom
alegauss:add-viglet-turing-es

Conversation

@alegauss

@alegauss alegauss commented Jul 10, 2026

Copy link
Copy Markdown

Adding Viglet Turing ES to the Search section.

Why it's distinct from the existing entries (Lucene/Solr/Elasticsearch): those are search libraries/engines. Turing ES is a full enterprise-search platform/application built on Spring Boot that runs on top of a pluggable Solr/Elasticsearch/Lucene backend and adds faceted + semantic + hybrid (RRF) search, RAG, and AI agents. It fills the application-layer gap in this category.


Summary by cubic

Add Viglet Turing ES to the Search section as an enterprise search platform (application layer), not a library. It runs on top of Solr/Elasticsearch/Lucene and includes faceted, semantic, and hybrid (RRF) search, RAG, and agents.

Written for commit 40eb786. Summary will update on new commits.

Review in cubic

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="README.md">

<violation number="1" location="README.md:1116">
P3: Consider removing the parenthetical `(not a library)` from the description. The CONTRIBUTING.md asks for descriptions that are "short, simple and unbiased." The parenthetical tells readers what the software isn't rather than what it does, and no other entry in the Search section uses this self-referential comparison pattern. The unique features that distinguish this entry (faceted, semantic and hybrid search, RAG, AI agents, pluggable backend) are already clearly stated in the rest of the line — the parenthetical adds length without adding signal.</violation>
</file>

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread README.md
- [Apache Solr](https://lucene.apache.org/solr/) - Enterprise search engine optimized for high-volume traffic.
- [Elasticsearch](https://www.elastic.co) - Distributed, multitenant-capable, full-text search engine with a RESTful web interface and schema-free JSON documents.
- [Indexer4j](https://github.com/haeungun/indexer4j) - Simple and light full text indexing and searching library.
- [Viglet Turing ES](https://github.com/openviglet/turing-ce) - Enterprise search platform (not a library): layers faceted, semantic and hybrid search, RAG and AI agents over a pluggable Apache Solr/Elasticsearch/Lucene backend.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: Consider removing the parenthetical (not a library) from the description. The CONTRIBUTING.md asks for descriptions that are "short, simple and unbiased." The parenthetical tells readers what the software isn't rather than what it does, and no other entry in the Search section uses this self-referential comparison pattern. The unique features that distinguish this entry (faceted, semantic and hybrid search, RAG, AI agents, pluggable backend) are already clearly stated in the rest of the line — the parenthetical adds length without adding signal.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At README.md, line 1116:

<comment>Consider removing the parenthetical `(not a library)` from the description. The CONTRIBUTING.md asks for descriptions that are "short, simple and unbiased." The parenthetical tells readers what the software isn't rather than what it does, and no other entry in the Search section uses this self-referential comparison pattern. The unique features that distinguish this entry (faceted, semantic and hybrid search, RAG, AI agents, pluggable backend) are already clearly stated in the rest of the line — the parenthetical adds length without adding signal.</comment>

<file context>
@@ -1113,6 +1113,7 @@ _Engines that index documents for search and analysis._
 - [Apache Solr](https://lucene.apache.org/solr/) - Enterprise search engine optimized for high-volume traffic.
 - [Elasticsearch](https://www.elastic.co) - Distributed, multitenant-capable, full-text search engine with a RESTful web interface and schema-free JSON documents.
 - [Indexer4j](https://github.com/haeungun/indexer4j) - Simple and light full text indexing and searching library.
+- [Viglet Turing ES](https://github.com/openviglet/turing-ce) - Enterprise search platform (not a library): layers faceted, semantic and hybrid search, RAG and AI agents over a pluggable Apache Solr/Elasticsearch/Lucene backend.
 
 ### Security
</file context>
Suggested change
- [Viglet Turing ES](https://github.com/openviglet/turing-ce) - Enterprise search platform (not a library): layers faceted, semantic and hybrid search, RAG and AI agents over a pluggable Apache Solr/Elasticsearch/Lucene backend.
- [Viglet Turing ES](https://github.com/openviglet/turing-ce) - Enterprise search platform: layers faceted, semantic and hybrid search, RAG and AI agents over a pluggable Apache Solr/Elasticsearch/Lucene backend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant