What is JPA? You are better off pulling from JPA yourself than coding with the DataImportHandler. It will be much easier.
EmbeddedSolr is just like web solr: when you commit data it is on the disk. If you crash during indexing, it may or may not be available to commit. EmbeddedSolr does not do anything special with index storage. Lance On Thu, May 19, 2011 at 2:08 AM, amit.b....@gmail.com <amit.b....@gmail.com> wrote: > Hi, > > We are trying build enterprise search solution using SOLR , out data source > is Database which is interfaced with JPA. > > Solution looks like > > SOLR INDEX > JPA > Oracle database. > > We need help to findout what is the best approch integrate Solr Index with > JPA. > > We tried out two appoches > > Approch 1 - > 1> Polulating SolrInputDocument with data from JPA > 2> Updating EmbeddedSolrServer with captured data using SolrJ API. > > Approch 2 - > 1> Customizing dataimporthandler of HTTPSolrServer > 2> Retrieving data in dataimporthandler using JPA entity. > > Functional requirement - > 1> Solution should be performant for huge magnitude of data > 2> Should be scalable > > We have few question which will help us to decide solution >>Will like know which one is better approch to meet our requirement. >>Is it good idea to integrate with Lucene against using EmbeddedSolrServer + > JPA >>If JVM is crashes , EmbeddedSolrServer content will be lost on reboot. >>Can we get support from Jasper Experts team ? can we buy ? how ? > > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SOLR-Custom-datasource-integration-tp2960475p2960475.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- Lance Norskog goks...@gmail.com
