RE: Ghost Documents or Shards out of Sync

nd what exactly you mean by "a message that one of the mandatory fields is missing" can you show us some details? solrconfig/schema, example documents, example updates, log messages from the various nodes when these updates "fail", etc... ? https://cwiki.apache.org/confluenc

RE: Ghost Documents or Shards out of Sync

hen atomic update succeeds. One more thing that might be important - we're using nested schema, and we recently encountered several issues that make me think that this combination - nested and atomic updates (of parent documents) - is the root cause. Ronen. -Original Message- From:

Re: Ghost Documents or Shards out of Sync

To expand on what Jason suggested, if the issue is the non-deterministic ordering due to staggered commits per replica, you may have more consistency with TLOG replicas rather than the NRT replicas. In this case, the underlying segment files should be identical and lead to more predictable results.

Re: Ghost Documents or Shards out of Sync

Forgot to answer your second question: > Can I trigger the "fixing" mechanism that Solr runs at restart by an API call > or some other method? It depends on what the cause is. But for at least some possible causes there is an API call that can resolve this. Though that API itself (Solr's misna

Re: Ghost Documents or Shards out of Sync

Hi Ronen, The first thing I'd figure out in your situation is whether the results are actually different each time, or whether the ordering is what differs (which might push a particular result off the page you're looking at, giving the appearance that it didn't match). In the case of the former,

Nested documents (parent,child,grandchild), multi-select facets

Hey all, I am having trouble finding current examples of multi-select faceting for nested documents. Specifically ones with *multiple *levels of nested documents. Any help/direction would be appreciated.Solr. 8.6 Hopefully my terminology is correct, I'm still new to solr. My current s

Re: Multi-select faceting for nested documents

Thanks for the response. I'll try and give a little more detail. Hopefully my terminology is correct, I'm still new to solr. My current schema has a parent document, two child documents(siblings), and a grandchild document. I am using the JSON API . Product ->

Re: Multi-select faceting for nested documents

21 at 10:34, Lance Snell wrote: > > Any examples would be greatly appreciated. > > On Mon, Jan 25, 2021, 2:25 AM Lance Snell wrote: > > > Hey all, > > > > I am having trouble finding current examples of multi-select faceting for > > nested documents. Specif

Re: Multi-select faceting for nested documents

Any examples would be greatly appreciated. On Mon, Jan 25, 2021, 2:25 AM Lance Snell wrote: > Hey all, > > I am having trouble finding current examples of multi-select faceting for > nested documents. Specifically ones with *multiple *levels of nested > documents. > > My

Ghost Documents or Shards out of Sync

Hi All, I'm using Solr Cloud (version 8.3.0) with shards and replicas (replication factor of 2). Recently, I've encountered several times that running the same query repeatedly yields different results. Restarting the nodes fixes the problem (until next time). I assume that some shards are not syn

Multi-select faceting for nested documents

Hey all, I am having trouble finding current examples of multi-select faceting for nested documents. Specifically ones with *multiple *levels of nested documents. My current schema has a parent document, two child documents(siblings), and a grandchild document. I am using the JSON API

Re: Events on updating documents

have a use-case > in which we want to hit a REST endpoint whenever documents are inserted, > updated, or deleted in Solr with the documents under consideration as well. > When exploring the Solr documentation, we found Event Listeners > <https://lucene.apache.org/solr/guide/6_6/upd

Events on updating documents

Hello, We at VNC are using Solr for search and as a data store. We have a use-case in which we want to hit a REST endpoint whenever documents are inserted, updated, or deleted in Solr with the documents under consideration as well. When exploring the Solr documentation, we found Event

Re: SPLITSHARD - data loss of child documents

ith child > documents, if that is missing from the ref guide we should update it > > On Thu, Dec 17, 2020 at 4:30 AM Nussbaum, Ronen > > wrote: > > > Hi Everyone, > > > > We're using version 8.6.1 with nested documents. > > I used the SPLITSHARD API

Re: SPLITSHARD - data loss of child documents

I was under the impression that split shard doesn’t work with child documents, if that is missing from the ref guide we should update it On Thu, Dec 17, 2020 at 4:30 AM Nussbaum, Ronen wrote: > Hi Everyone, > > We're using version 8.6.1 with nested documents. > I used the S

SPLITSHARD - data loss of child documents

Hi Everyone, We're using version 8.6.1 with nested documents. I used the SPLITSHARD API and after it finished successfully, I've noticed the following: 1. Most of child documents are missing - before the split: ~600M, after: 68M 2. Retrieving a document with its children, s

Re: Atomic update wrongly deletes child documents

ow using a custom UpdateRequestProcessor that removes undefined fields, so that I was able to remove the catch-all dynamic field "ignored" from my schema.. Of course, one has to be careful to not remove fields that are used for nested documents in the URP. I think it would still m

Re: Atomic update wrongly deletes child documents

e the catch-all dynamic field "ignored" from my schema.. Of course, one > has to be careful to not remove fields that are used for nested documents in > the URP. > > I think it would still make sense to fix the original issue, or at least > document it as caveat. I'm go

Re: Atomic update wrongly deletes child documents

Hi, I was able to work around the issue. I'm now using a custom UpdateRequestProcessor that removes undefined fields, so that I was able to remove the catch-all dynamic field "ignored" from my schema.. Of course, one has to be careful to not remove fields that are used for nested d

Atomic update wrongly deletes child documents

Hi, when I try to atomically update a single field of a parent/root document, all of its nested child documents disappear (Solr 8.6.3). I've tracked the problem down to the reconstruction of the original document in DistributedUpdateProcessor#getUpdatedDocument. Solr correctly

Child documents are not retrieved after DIH

I will try to explain myself in as much detail as possible and isolating as much as possible from the context. Shortly, I'm trying to create a `DIH` in order to digest some documents as nested. I mean, I need to digest an `one-to-many` relation and put it as nested documents. My `parents`

Filtering Parent documents based on Child documents Facets selection

I have a nested documents which I am syncing in Solr : { "id":"NCT04372953", "title":"Positive End-Expiratory Pressure (PEEP) Levels During Resuscitation of Preterm Infants at Birth (The POLAR Trial) ", "phase":"N/A", &

Solr 8.6.2 Facets query for Nested documents

Hello Team, I have sync following nested document in Solr 8.6.2. { "id":"NCT04372953", "title":"Positive End-Expiratory Pressure (PEEP) Levels During Resuscitation of Preterm Infants at Birth (The POLAR Trial) ", "phase":"N/A", "status":"Not yet recruiting", "studytype":"Intervent

Re: Index Deeply Nested documents and retrieve a full nested document in solr

ne please help to index the below sample json document into Solr. > > I have following queries on indexing multi level child document. > > > 1. Can we specify names to documents hierarchy such as "therapeuticareas" > or "sites" while indexing. > 2. How

Index Deeply Nested documents and retrieve a full nested document in solr

Hello Team, Can someone please help to index the below sample json document into Solr. I have following queries on indexing multi level child document. 1. Can we specify names to documents hierarchy such as "therapeuticareas" or "sites" while indexing. 2. How can

Retrieving Parent and Child Documents using the Bock Join Query Technique when the Child and parent Document having the identical field

Hi Solr Team, I am trying to retrieve the Parent Document by using the Block Join Parent Query Parser (q={!parent which=allParents}someChildren), but the filter condition i gave is having the same field in both the parent and the child document, So the Parser is throwing the Error : "Child qu

Child query with negative filter return zero documents

Hi! We have documents with one level of child documents. One use case we have is returning (or getting stats for) child documents, filtering by field values on both the child and the parent. This works for «must» filter on parent: q= *:* fq=doc_type:child fq=child_field:child_field_value fq

Re: [Subquery] Transform Documents across Collections

is a _core_ not a >> collection. See: >> >> https://lucene.apache.org/solr/guide/8_2/transforming-result-documents.html >> >> It’s vaguely possible you could make it work by specifying something like >> fromIndex=Collection2_shard1_replica_n1 >> if it wa

Re: [Subquery] Transform Documents across Collections

> > Sorry, I was in a hurry to create a simple enough yet similar case that > we > > face with internally. > > > > reporting_to indeed is the right field , but the same error still > persists, > > something is seemingly wrong when invoking the *subquery *with >

Re: [Subquery] Transform Documents across Collections

ny help much appreciated, hopefully it's an error with the syntax I've > been using. > > Regards, > Norbert > > On Wed, 12 Aug 2020 at 12:49, Dominique Bejean > wrote: > >> Hi Norbert, >> >> The field name in collection2 is "reporting_to" n

Re: [Subquery] Transform Documents across Collections

Hi Norbert, > > The field name in collection2 is "reporting_to" not "reporting". > > Dominique > > > > Le mer. 12 août 2020 à 11:59, Norbert Kutasi a > écrit : > > > Hello, > > > > We have been using [subquery] to come up with arbitrary c

Re: [Subquery] Transform Documents across Collections

es. > > It works well as long as the documents are in the same collection however > based on the reference guide I infer it can bring in documents from > different collections except it throws an error. > > https://lucene.apache.org/solr/guide/8_2/transforming-result-documents.

[Subquery] Transform Documents across Collections

Hello, We have been using [subquery] to come up with arbitrary complex hierarchies in our document responses. It works well as long as the documents are in the same collection however based on the reference guide I infer it can bring in documents from different collections except it throws an

Re: Max number of documents in update request

to pursue much. See: > > > > https://lucidworks.com/post/really-batch-updates-solr-2/ > > > > If you’re looking at trying to maximize throughput, adding > > client threads that send Solr documents is a better approach. > > > > All that said, I usually just

Re: Max number of documents in update request

not answerable. 1K docs? 1G docs? 1 field or 500? > > And I don’t think it’s a good use of time to pursue much. See: > > https://lucidworks.com/post/really-batch-updates-solr-2/ > > If you’re looking at trying to maximize throughput, adding > client threads that send Solr docu

Re: Max number of documents in update request

, adding client threads that send Solr documents is a better approach. All that said, I usually just pick 1,000 and don’t worry about it. Best, Erick > On Jul 7, 2020, at 8:59 AM, Sidharth Negi wrote: > > Hi, > > Could someone help me with the best way to go about determining the maxi

Max number of documents in update request

Hi, Could someone help me with the best way to go about determining the maximum number of docs I can send in a single update call to Solr in a master / slave architecture. Thanks!

RE: Atomic updates with nested documents

10, 2020 11:10 AM To: solr-user@lucene.apache.org Subject: AW: Atomic updates with nested documents Hi Adi, thank you for your reply! Although I have to admit that this is not the response that I was hoping for 😊. Upgrading to Solr 8 is currently not possible for us because we found multiple

AW: Atomic updates with nested documents

: München Handelsregisternummer: HRB 163761 --- -Ursprüngliche Nachricht- Von: Kaminski, Adi Gesendet: Sonntag, 7. Juni 2020 08:45 An: solr-user@lucene.apache.org Betreff: RE: Atomic updates with nested documents Hi Ludger, We had the same issue with Solr 7.6, and after discussing with the

RE: Atomic updates with nested documents

the above mentioned changes. Regards, Adi -Original Message- From: Ludger Steens Sent: Friday, June 5, 2020 3:24 PM To: solr-user@lucene.apache.org Subject: Atomic updates with nested documents Dear Community, I am using Solr 7.7 and I am wondering how it is possible to do a partia

Atomic updates with nested documents

Dear Community, I am using Solr 7.7 and I am wondering how it is possible to do a partial update on nested documents / child documents. Suppose I have committed the following documents to the index: [ { "id": "1", "testString": "1",

Re: Insert documents to a particular shard

;> particular shard , I read about implicit and composite route but i don't > >> think it will work for my usecase. > >> > >> shard1 : http://192.168.0.112:8983/family_shard1_replica_n1 > >> http://192.168.0.112:7574/family_shard1_replica_n2 > >> > >

Re: Insert documents to a particular shard

rticular shard , I read about implicit and composite route but i don't >> think it will work for my usecase. >> >> shard1 : http://192.168.0.112:8983/family_shard1_replica_n1 >> http://192.168.0.112:7574/family_shard1_replica_n2 >> >> shard2: http://

Re: Insert documents to a particular shard

n2 > > shard2: http://192.168.0.112:8983/family_shard2_replica_n3 > http://192.168.0.112:7574/family_shard2_replica_n4 > > we have documents with parent child relationship but flatten out with 2 > levels down and reference to each other. > family schema document

Insert documents to a particular shard

:8983/family_shard1_replica_n1 http://192.168.0.112:7574/family_shard1_replica_n2 shard2: http://192.168.0.112:8983/family_shard2_replica_n3 http://192.168.0.112:7574/family_shard2_replica_n4 we have documents with parent child relationship but flatten out with 2 levels down and reference to each

Re: Fetch related documents from Custom Function

Solr Experts, any easy way for reading other solr docs ( other docs ) from solr custom function ? -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Fetch related documents from Custom Function

Yes. But being inside solr ( I mean code getting executing via Custom function ), do we have option to read the other solr documents in a easy way. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Fetch related documents from Custom Function

Hello, It sounds either like classic denormalization or (little bit slow and cumbersome) result transformer [subquery]. On Mon, May 18, 2020 at 4:04 PM mganeshs wrote: > Is there a easy possibility of reading the few field from related documents > from Custom function ? > > For

Fetch related documents from Custom Function

Is there a easy possibility of reading the few field from related documents from Custom function ? For ex, Project document contains, project id, project name, Project manager id ( which is nothing but employee id ). & Employee document contains field ( Employee id, Employee name ). Now w

Search on Nested Documents

Hi I have gone through https://lucene.apache.org/solr/guide/8_5/searching-nested-documents.html and examples suggest to search on a field either on parent or child based on parsers. Is there a way to search on the combined text of parent and child documents? Assume below is the document I am

Give boosting to a grouped documents in Solr Based on number of results in a group

2 because he has more number of products related to mobile phones. Is there a way in Solr where I can boost a supplier and give boosting to a grouped documents in Solr Based on the number of results in a group. Any help will be appreciated. -- Thanks & Regards, Ajay Sharma Software Engi

Re: Inconsistent / confusing documentation on indexing nested documents.

: Is the documentation wrong or have I misunderstood it? The documentation is definitely wrong, thanks for pointing this out... https://issues.apache.org/jira/browse/SOLR-14383 -Hoss http://www.lucidworks.com/

Inconsistent / confusing documentation on indexing nested documents.

Hi, The page "Indexing Nested Documents" has an XML example showing two different ways of adding nested documents: https://lucene.apache.org/solr/guide/8_5/indexing-nested-documents.html#xml-examples The text says: "It illustrates two styles of adding child documents: the firs

Re: number of documents exceed 2147483519

time. Why? Thanks. From: Hongxu Ma Sent: Monday, March 16, 2020 16:46 To: solr-user@lucene.apache.org Subject: number of documents exceed 2147483519 Hi I'm using solr-cloud (ver 6.6), got an error: org.apache.solr.common.SolrException: Exception writing document id (null) to the index;

number of documents exceed 2147483519

Hi I'm using solr-cloud (ver 6.6), got an error: org.apache.solr.common.SolrException: Exception writing document id (null) to the index; possible analysis error: number of documents in the index cannot exceed 2147483519 After googled it, I know the number is exceed one solr shard limit

Denormalize Nested Documents

Hello All, We are storing nested documents in Solr and when we query we would like to get denormalized (flattened ) view of nested object. For ex Stored Document : 1. { 2. course: "Java", 3. room: "10", 4. students: [ 5. { 6. id: 12, 7. name: "Jo

Re: Mix Index having child-free and nested documents

child-free and with-child documents, > sample xml: > > > 4 > Regular Shirt > Parent > Black > > > 8 > Solid Rug > Parent > Solid > > > 1 > Regular color Shirts > Parent > > > 2 > Child > Red> > > > 3 > Child >

Mix Index having child-free and nested documents

I have a solr core which has a mix of child-free and with-child documents, sample xml: 4 Regular Shirt Parent Black 8 Solid Rug Parent Solid 1 Regular color Shirts Parent 2 Child Red> 3 Child Blue> 5 Rugs Parent 6 Child Abstract 7 Child Printed Now i want to write a

Re: Bug? Documents not visible after sucessful commit - chaos testing

Hi Chriss, thanks for opening the ticket. I have found some possibly related issues: Open: https://issues.apache.org/jira/browse/SOLR-3888 - "need beter handling of external add/commit requests during tlog recovery" Closed: https://issues.apache.o

Re: Bug? Documents not visible after sucessful commit - chaos testing

: We think this is a bug (silently dropping commits even if the client : requested "waitForSearcher"), or at least a missing feature (commits beging : the only UpdateRequests not reporting the achieved RF), which should be : worth a JIRA Ticket. Thanks for your analysis Michael -- I agree someth

Re: [External] Re: per-field count of documents matched?

> supports don't include fancy Booleans, so your ideas just might work > > Thanks again, > Steve > > -Original Message- > From: Erick Erickson > Sent: Tuesday, February 11, 2020 7:16 PM > To: solr-user@lucene.apache.org > Subject: [External] Re: per-f

Re: Bug? Documents not visible after sucessful commit - chaos testing

d Your > Writes" for a clear point in time - which in our understand should be after > hard commits with waitSearcher=true return sucessfull from all replicas. Is > that correct? > The client that indexes new documents performs a hard commit with > waitSearcher=true and af

RE: [External] Re: per-field count of documents matched?

e.org Subject: [External] Re: per-field count of documents matched? Hmmm, you could do a facet query (or a series of them). facet.query=LastName:stone&facet.query=Street:stone etc….. That’d automatically only tally for the docs that match. You could also consider a custom search component. For

Re: per-field count of documents matched?

above. I’m still not sure it’s what you need, since I’m not sure what "per-field count of documents that match” means in your application… Best, Erick > On Feb 11, 2020, at 6:15 PM, Fischer, Stephen > wrote: > > Hi wise Solr experts, > > For our scientific use-case

per-field count of documents matched?

Hi wise Solr experts, For our scientific use-case we want to show users a per-field count of documents that match that field. We like to do this efficiently because we might return up to a million documents. For example, if we had documents describing People, and a query of, say, "Ston

Re: Bug? Documents not visible after sucessful commit - chaos testing

should be after hard commits with waitSearcher=true return sucessfull from all replicas. Is that correct? The client that indexes new documents performs a hard commit with waitSearcher=true and after that was successful, we expect the documents to be visible on all Replicas. This seems to work as

Re: Bug? Documents not visible after sucessful commit - chaos testing

e using 'rf' ... seeing exactly how you create your collection is important to make sure we're talking about the same thing. : Each "transaction" adds, modifys and deletes documents and we ensure that : each response has a "rf=2" (achieved replication factor=2) at

Bug? Documents not visible after sucessful commit - chaos testing

Hi All, In our Solr Cloud cluster (8.4.1) sometimes committed documents are not visible to subsequent requests sent after a, apprently, sucessful commit(waitFlush=true, wait=searcherTrue). This behaviour does not happen if all nodes are stable, but will happen eventually if we kill off random

Solr Nested Documents not properly working

Could you please answer my question on https://stackoverflow.com/questions/59566421/solr-nested-documents-not-properly-setup Thank you. Yirmiyahu Fischer Senior Developer Signature IT

Re: sorting groups on the basis of average of a field in documents

> > > Hi All, > > > > I have a requirement where I need to sort the group on average of a > > particular field. > > The motive here is to compute the average of the value of a field across > > all documents of the group and then sort the group on the basis of &

Re: sorting groups on the basis of average of a field in documents

gt; > I have a requirement where I need to sort the group on average of a > particular field. > The motive here is to compute the average of the value of a field across > all documents of the group and then sort the group on the basis of > commuted average. > > Is there any app

sorting groups on the basis of average of a field in documents

Hi All, I have a requirement where I need to sort the group on average of a particular field. The motive here is to compute the average of the value of a field across all documents of the group and then sort the group on the basis of commuted average. Is there any approach that can be used to

Re: Does CloudMLTQParser support getting related documents from different shards?

charge of parsing the query and, in this case getting the relevant from the indicated document to add to the query while doing some sanity checking. The bits that distribute the query to shards and collate the results are elsewhere. * AFAIK, the part that fetches the relevant documents is following

Re: Does CloudMLTQParser support getting related documents from different shards?

he code though, > https://github.com/apache/lucene-solr/blob/2d690885e554dda7b4b4e0f46f2bd9cacdb32df6/solr/core/src/java/org/apache/solr/search/mlt/CloudMLTQParser.java > , > it seems like that for the document for which we are finding out related > documents, that document is getting

Does CloudMLTQParser support getting related documents from different shards?

/CloudMLTQParser.java , it seems like that for the document for which we are finding out related documents, that document is getting fetched now with real-time get request handler. core.getRequestHandler("/get").handleRequest(request, rsp); This is good because now that document will get fetche

Re: updating documents via csv

Oh lol. How could I miss that! This is actually true for any bash command. Glad that it worked. On Wed, 18 Dec, 2019, 00:29 rhys J, wrote: > On Mon, Dec 16, 2019 at 11:58 PM Paras Lehana > wrote: > > > Hi Rhys, > > > > I use CDATA for XMLs: > > > > > > > > > > There should be a similar so

Re: updating documents via csv

On Mon, Dec 16, 2019 at 11:58 PM Paras Lehana wrote: > Hi Rhys, > > I use CDATA for XMLs: > > > > > There should be a similar solution for JSON though I couldn't find the > specific one on the internet. If you are okay to use XMLs for indexing, you > can use this. > > We are set on using js

Re: updating documents via csv

Hi Rhys, I use CDATA for XMLs: There should be a similar solution for JSON though I couldn't find the specific one on the internet. If you are okay to use XMLs for indexing, you can use this. On Tue, 17 Dec 2019 at 01:40, rhys J wrote: > Is there a way to update documents

updating documents via csv

Is there a way to update documents already stored in the solr cores via csv? The reason I am asking is because I am running into a problem with updating via script with single quotes embedded into the field itself. Example: curl http://localhost:8983/solr/dbtr/update?commit=true -d '[

SOLR: when trying to delete all documents, error response body is a html string. How can I get json instead?

Details: https://stackoverflow.com/questions/59337583/solr-when-trying-to-delete-all-documents-error-response-body-is-in-html-string Thank you!

Re: Prevent Solr overwriting documents

That would be “do-not-overwrite”. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Nov 27, 2019, at 4:38 PM, Walter Underwood wrote: > > Even if that works, it is evil as something to leave in a client codebase. > Maybe a do-no-overwrite flag would

Re: Prevent Solr overwriting documents

Even if that works, it is evil as something to leave in a client codebase. Maybe a do-no-overwrite flag would be useful. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Nov 27, 2019, at 3:24 PM, Alexandre Rafalovitch wrote: > > How about Optimistic

Re: Prevent Solr overwriting documents

Oops. And the link... https://lucene.apache.org/solr/guide/6_6/updating-parts-of-documents.html#UpdatingPartsofDocuments-OptimisticConcurrency On Wed, Nov 27, 2019, 6:24 PM Alexandre Rafalovitch, wrote: > How about Optimistic Concurrency with _version_ set to negative value? > > You could inject

Re: Prevent Solr overwriting documents

How about Optimistic Concurrency with _version_ set to negative value? You could inject that extra value in URP chain if need be. Regards, Alex On Wed, Nov 27, 2019, 5:41 PM Aaron Hoffer, wrote: > We want to prevent Solr from overwriting an existing document if document's > ID already exis

Prevent Solr overwriting documents

We want to prevent Solr from overwriting an existing document if document's ID already exists in the core. This unit test fails because the update/overwrite is permitted: public void testUpdateProhibited() { final Index index = baseInstance(); indexRepository.save(index); Index index0 = ind

Re: fq pfloat_field:* returns no documents, tfloat:* does

On 11/21/2019 7:48 AM, Webster Homer wrote: Thank you. Why don't point fields get loaded by the Schema Browser's "Load Term Info" button? From what I've seen in the past on discussions, Point-based fields are missing Term data. There's literally nothing to load. https://issues.apache.org/j

Fetching Parent-Child documents - Solr 8.2

. I am trying http://localhost:8983/solr/demo/select?fl=*,[child]&q={!parent<http://localhost:8983/solr/demo/select?fl=*,%5bchild%5d&q=%7B!parent> which="cat_s:sci-fi AND pubyear_i:1992"} what are the ways to retrieve parent child as nested documents? We need to

RE: fq pfloat_field:* returns no documents, tfloat:* does

Thank you. Why don't point fields get loaded by the Schema Browser's "Load Term Info" button? -Original Message- From: Tomás Fernández Löbbe Sent: Wednesday, November 20, 2019 4:38 PM To: solr-user@lucene.apache.org Subject: Re: fq pfloat_field:* returns no document

Re: fq pfloat_field:* returns no documents, tfloat:* does

Hi Webster, > The fq facet_melting_point:* "Point" numeric fields don't support that syntax currently, and the way to retrieve "docs with any value in field foo" is "foo:[* TO *]". See https://issues.apache.org/jira/browse/SOLR-11746 On Wed, Nov 20, 2019 at 2:21 PM Webster Homer < webster.ho...@

fq pfloat_field:* returns no documents, tfloat:* does

The fq facet_melting_point:* Returns 0 rows. However the field clearly has data in it, why does this query return rows where there is data I am trying to update our solr schemas to use the point fields instead of the trie fields. We have a number of pfloat fields. These fields are indexed and

Multiple versions of same documents with different effective dates

Hello, I am trying to keep multiple versions of same document (empId, empName,deptID,effectiveDt,empTitle..,..) with different effective dates (composite key: deptID,empID,effectiveDt) but mark/ soft delete (deleted=Y) the older ones and keep deleted=N for the latest one. This way i can query the

Re: Delete documents from the Solr index using SolrJ

wly added > docs. I hope this is possible, but how ? > Because, currently I am using SolrJ and it re-index complete data each time. > > -Original Message- > From: Peter Lancaster [mailto:peter.lancas...@findmypast.com] > Sent: 04 November 2019 21:35 > To: solr-user@luc

RE: Delete documents from the Solr index using SolrJ

November 2019 21:35 To: solr-user@lucene.apache.org Subject: RE: Delete documents from the Solr index using SolrJ You can delete documents in SolrJ by using deleteByQuery. Using this you can delete any number of documents from your index or all your documents depending on the query you specify as the

Re: Delete documents from the Solr index using SolrJ

com] >> Sent: 04 November 2019 20:04 >> To: solr-user@lucene.apache.org >> Subject: Re: Delete documents from the Solr index using SolrJ >> >> when you add a new document using the same "id" value as another it just >> over writes it >> >&

Re: Delete documents from the Solr index using SolrJ

20:04 > To: solr-user@lucene.apache.org > Subject: Re: Delete documents from the Solr index using SolrJ > > when you add a new document using the same "id" value as another it just over > writes it > > On Mon, Nov 4, 2019 at 9:30 AM Khare, Kushal (MIND) < > kus

RE: Delete documents from the Solr index using SolrJ

You can delete documents in SolrJ by using deleteByQuery. Using this you can delete any number of documents from your index or all your documents depending on the query you specify as the parameter. How you use it is down to your application. You haven't said if your application perfo

RE: Delete documents from the Solr index using SolrJ

carry on with the solution that you proposed. Please guide ! -Original Message- From: David Hastings [mailto:hastings.recurs...@gmail.com] Sent: 04 November 2019 20:10 To: solr-user@lucene.apache.org Subject: Re: Delete documents from the Solr index using SolrJ delete them by query would

Re: Delete documents from the Solr index using SolrJ

In my case, id won't be same. > Suppose, I have a doc with id : 20 > Now, it's newer version would be either 20.1 or 22 > What in this case? > -Original Message- > From: David Hastings [mailto:hastings.recurs...@gmail.com] > Sent: 04 November 2019 20:04 > To: solr

RE: Delete documents from the Solr index using SolrJ

ubject: Re: Delete documents from the Solr index using SolrJ when you add a new document using the same "id" value as another it just over writes it On Mon, Nov 4, 2019 at 9:30 AM Khare, Kushal (MIND) < kushal.kh...@mind-infotech.com> wrote: > Could you please le

RE: Delete documents from the Solr index using SolrJ

more clear now. -Original Message- From: Khare, Kushal (MIND) [mailto:kushal.kh...@mind-infotech.com] Sent: 04 November 2019 20:00 To: solr-user@lucene.apache.org Subject: RE: Delete documents from the Solr index using SolrJ Could you please let me know how to achieve that

  1   2   3   4   5   6   7   8   9   10   >