Announcement

Collapse
No announcement yet.

Solr considerations

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Solr considerations

    Any thought to a solr api to voltdb?

  • #2
    Lucene/Solr

    We heard one use-case for lucene/text indexes over a subset of a VoltDB table. We have not explored this in depth.


    I see a few possible integrations.


    1. Generate text search indexes on selected columns at a partition. This would allow text searches within a partition relatively efficiently. It would not make global multi-partiton text search fast (it would be dominated by the mult-partition transaction cost). Our storage layer is C++ based. Integrating lucene, a Java project, at this layer is non-trivial.


    2. Allow Solr/Lucene to pull and index VoltDB data. This is requires exporting data from VoltDB in an efficient way for storage and indexing in a solr/lucene store. We have live export functionality in VoltDB (you can pull a stream of table changes while VoltDB is running). We have not explored how well export would work with Solr or what kind of update stream would be friendliest to Solr.


    I'm not familiar with Solr, beyond a couple hours of reading. Perhaps if (1) were accomplished, a more sophisticated integration would be feasible, with Solr using VoltDB as its backing-store. This is speculation on my part and not based on a technical understanding of Solr.

    Comment


    • #3
      Take a look at solandra - cassandra + solr/lucene

      http://blog.sematext.com/2010/02/09/...ucene-backend/


      https://github.com/tjake/Solandra --


      This works really well - but the idea could translate well to using VoltDb as a backend - in many ways it may be a better fit the cassandra is.

      Comment

      Working...
      X