Lucene update document by id

However, In some situations users may want to configure their own document specific version field, where the version values are assigned on a per-document basis by an external system, and have Solr reject updates that attempt to replace a document with an "older" version.

Users can not re-purpose that field and specify it as the versionField for use in the DocBasedVersionConstraintsProcessorFactory configuration. DocBasedVersionConstraintsProcessorFactory supports two additional configuration params which are optional:.

If set to true then instead of rejecting updates where the versionField is too low, the update will be silently ignored and return a status to the client. The value of this configuration option should be the name of a request parameter that the processor will now consider mandatory for all attempts to Delete By Id, and must be be used by clients to specify a value for the versionField which is greater then the existing value of the document to be deleted. When using this request param, any Delete By Id command with a high enough document version number to succeed will be internally converted into an Add Document command that replaces the existing document with a new one which is empty except for the Unique Key and versionField to keeping a record of the deleted version so future Add Document commands will fail if their "new" version is not high enough.

Toggle navigation Solr Ref Guide 6. Updating Parts of Documents. Atomic Updates Solr supports several modifiers that atomically update values of a document.

May be specified as a single value, or as a list for multiValued fields. Removes all occurrences of the specified values from a multiValued field. Removes all occurrences of the specified regex from a multiValued field.

Example If the following document exists in our collection:. In-Place Updates In-place updates are very similar to atomic updates; in some sense, this is a subset of atomic updates. Example If the price and popularity fields are defined in the schema as:. In general, using optimistic concurrency involves the following work flow:. A client changes the document locally.

If there is a version conflict HTTP error code , the client starts the process over. Adds the specified values to a multiValued field. Syntactically, updates changing the children of a document are very similar to regular atomic updates of simple fields, as demonstrated by the examples below. Schema and configuration requirements for updating child documents use the same Field Storage requirements for atomic updates mentioned above.

You can expect more overhead because of this. In-place updates avoid that. When SolrCloud receives document updates, the document routing rules for the collection is used to determine which shard should process the update based on the id of the document. When sending an update that specifies the id of a child document this will not work by default: the correct shard to send the document to is based on the id of the "Root" document for the block the child document is in, not the id of the child document being updated.

This is how Solr understands that you are updating a child document, and not a Root document. All of the Atomic Update operations mentioned above are supported for "real" fields of Child Documents:. As with normal multiValued fields, the set keyword can be used to replace all child documents in a psuedo-field:.

As with normal multiValued fields, the add keyword can be used to add additional child documents to a psuedo-field:. In-place updates are very similar to atomic updates; in some sense, this is a subset of atomic updates.

In regular atomic updates, the entire document is reindexed internally during the application of the update. However, in this approach, only the fields to be updated are affected and the rest of the documents are not reindexed internally. Hence, the efficiency of updating in-place is unaffected by the size of the documents that are updated i. Apart from these internal differences in efficiency, there is no functional difference between atomic updates and in-place updates.

An atomic update operation is performed using this In-Place approach only when the fields to be updated meet these three conditions:. To use in-place updates, add a modifier to the field that needs to be updated. The content can be updated or incrementally increased.

Since it can be tricky to ensure that all of the necessary conditions are satisfied to ensure that an update can be done In-Place, Solr supports a request parameter option named update. When set to true , an atomic update that can not be done In-Place will fail. Specific semantics are used to define when the document should be updated or when to report a conflict. In this case, no version matching occurs, but if the document does not exist, the updates will be rejected.

In this case, no version matching occurs, but if the document exists, the updates will be rejected. Lucene - Update Document Operation Advertisements. Previous Page. Next Page. Previous Page Print Page. Save Close. Clean and Build the application to make sure business logic is working as per the requirements.