Skip to main content

Integrate Apache Solr search results with enterprise data with Teiid

Apache Solr is a full text search engine built on top of Apache Lucene for indexing and searching any data contents. This is been widely used by many organisations for their searching needs.

Typically when a user wants to use Apache Solr, they will configure an instance of Apache Solr or SolrCloud with relevant indexing fields and publish all their data/documents that instance to be indexed. Once the documents are indexed, they can use Solr APIs to search the documents and use it for their purposes. This is where I believe Teiid can help ease the uploading of the enterprise data and with integration of search results with other data sources.

Starting with Teiid 8.7.Alpha1, Teiid provides translator for Apache Solr. Using this translator, user can 

  1. Continually add/update the documents in the search system from other sources automatically.
  2. If the search fields are stored in Solr system, this can be used as very low latency data retrieval for serving high traffic applications
  3. Solr translator be used as fast full text search, where the Solr document only contained the index information, then use the results as inverted index to gather target full documents from the other enterprise sources such as RDBMS, Web Service, SalesForce etc, all in single client call transparently with out any coding.
To illustrate this integration in an example I wrote this article, please read on.. Integrate Apache Solr with Teiid

Let us know if you have any comments or questions in Teiid forums.




Popular posts from this blog

Teiid Runtimes Explained

If you have been following Teiid lately we have been going through a whole lot of renovations. Yes, renovations or reorganization or refactoring or whatever you want to call it. Basically, we are making Teiid more modular with fewer dependencies that can be used by however your use case dictates rather than use it as one monolith application deployed into WildFly JEE Application Server. There is nothing wrong in using Teiid as server model, but with the proliferation of container-based workloads and cloud-based architectures, the previous server-based model does not work or simply won't scale. So, we needed to think of alternatives, thus Teiid team introduced a couple different versions modular Teiid what we are calling as "Teiid Runtimes".

Note that in these modular Teiid runtimes, not all the features you were used to using in Teiid Server model may not be there but you will have extensions to add in those that are most appropriate for your domain. If you are looking …

Teiid Platform Sizing Guidelines and Limitations

Users/customers always ask us about the sizing of their Data Virtaulization infrastructure based on Teiid or the JDV product from Redhat. Typically this is very involved question and not a very easy one answer in plain terms. This is due to fact that it involves taking into consideration questions like:
What kind of sources that user is working with? Relational, file, CRM, NoSQL etc.How many sources they are trying to integrate? 10, 20, 100?What are the volumes of data they are working with? 10K, 100K, 1M+?What are the query latency times from the sources? How you are using Teiid to implement the data integration/virtualization solution. What kind of queries that user is executing? Even small federated results may take a lot of server side processing - especially if the plan needs tweaking.Is materializing being used?Is query written in optimal way?and so on..Each and every one of the question affects the performance profoundly, and if you got mixture of those then it become that much…