Query regarding integrating solr query functions into blockfacetjoin Query
he expression '* {!boost}(+{!lucene v=$yq} {!func v=$yab})*' functions in the block join facting query -"*q={!parent%20which=%22itemtype_string:Product%22} itemtype_string:TierPrice&wt=json&indent=true&facet=true&child.facet.field=contract_string&rows=500*" ? I shall be highly grateful if someone can suggest to me some insight. Thanks & Regards, Ravi Kumar SAP Hybris Consultant
Re: Solr indexing with Tika DIH - ZeroByteFileException
Hi, Iam also facing same issue. Does anyone have any update/soulution how to fix this issue as part DIH? Thanks. Regards, Ravi kumar -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
2 Solr Instance with One Data Directory
Hi Any one tried, have 2 solr Instance with One Data Directory. I get below Error when i try to point the 2nd solr to the first solr directory. Any help ? org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Index dir '/engine/data/index/' of core 'engine' is already locked. The most likely cause is another Solr server (or another solr core in this server) also configured to use this directory; other possible causes may be specific to lockType: native Thanks Ravi
Solr in NAS or Network Shared Drive
Hello, Scenario: Currently we have 2 Solr Servers running in 2 different servers (linux), Is there any way can we make the Core to be located in NAS or Network shared Drive so both the solrs using the same Index. Let me know if any performance issues, our size of Index is appx 1GB. Thanks Ravi -Original Message- From: biplobbiswas [mailto:revolutionisme+s...@gmail.com] Sent: Friday, May 19, 2017 9:23 AM To: solr-user@lucene.apache.org Subject: Re: Nested Document is flattened even with @Field(child = true) annotation Hi Mikhail Khludnev-2 wrote > Hello, > > You need to use > https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherPa > rsers-BlockJoinQueryParsers > and > https://cwiki.apache.org/confluence/display/solr/Transforming+Result+D > ocuments#TransformingResultDocuments-[child]-ChildDocTransformerFactor > y > to get the nested data back. > > > -- > Sincerely yours > Mikhail Khludnev I had already gone through those links you posted and they talk about retrieving after indexing. My problem is that my documents are not indexed in a nested structure. Can you please look at the first comment as well where I posted a sample code and sample response which i get back. Because its creating distinct documents for nested structure -- View this message in context: http://lucene.472066.n3.nabble.com/Nested-Document-is-flattened-even-with-Field-child-true-annotation-tp4335877p4335891.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Multiple cores or not?
Hi, The architecture is probably better served depending on the content and data sources. If you have multiple data sources for each of the sites.. e.g database serving up site content, Feeds serving up syndicated content , then multicore will be better served using each core by data source core1-> database core2 -> RSS As with multiple sites, you can run multiple solr indexes with each index serving a website, Alternatively if you have common content across the sites, then you could use one of the cores to serve common content with other cores service site specific content. Hope this info helps. Regards, Ravi From: Otis Gospodnetic To: solr-user@lucene.apache.org Sent: Thu, July 15, 2010 4:56:24 AM Subject: Re: Multiple cores or not? Hello there, I'm guessing the sites will be searched separately. In that case I'd recommend a core for each site. Otis Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Lucene ecosystem search :: http://search-lucene.com/ - Original Message > From: "scr...@asia.com" > To: solr-user@lucene.apache.org > Sent: Wed, July 14, 2010 3:02:36 PM > Subject: Multiple cores or not? > > > > > Hi, > > We are planning to host on same server different website that will use solr. > > What will be the best? > > One core with a field i schema: site1, site2 etc... and then add this in > every > >query > > Or one core per site? > > Thanks for your help > > > >