Solr is not a database. I strongly recommend that you NOT use it as a data
store. You will lose data.
Solr does not have transactions. Don’t think of a Solr “commit” as a database
commit. It is a command to start indexing the queued updates. It does not even
attempt to meet ACID properties.
Re
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 Listener
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
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
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 already stored
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 '[{ "id":
"35
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 3/2/18 7:46 PM, Shawn Heisey wrote:
> On 3/2/2018 10:39 AM, Christopher Schultz wrote:
>> The problem is that I'm updating the index after my SQL UPDATE(s)
>> have run, but before my SQL COMMIT occurs. I have had a problem
>> where the SQL
On 3/2/2018 10:39 AM, Christopher Schultz wrote:
> The problem is that I'm updating the index after my SQL UPDATE(s) have
> run, but before my SQL COMMIT occurs. I have had a problem where the SQL
> fails and rolls-back, but the solrClient is not rolled-back.
>
> I'm a little wary of rolling-back S
Hey, folks. I've been a long-time Lucene user (running a hilariously-old
1.9.1 version forever), but I'm only just now getting into using Solr.
My particular use-case is storing information about web-application
users so they can be found more quickly than our current RDBMS-based
search (SELECT ..
I'm pretty sure that atomic updates use Real Time Get which means they'll
pull the values from in-memory structures for docs that haven't been
committed yet.
And as Shawn says, docValues isn't relevant here.
Best,
Erick
On Thu, Nov 17, 2016 at 5:52 AM, Shawn Heisey wrote:
> On 11/17/2016 6:26 A
On 11/17/2016 6:26 AM, Dorian Hoxha wrote:
> Looks like you can update documents even using just doc-values
> (without stored). While I understand the columnar-format, my issue
> with this is that docValues are added when a 'commit' is done
> (right?). Does that mean that it will force a commit (wh
Looks like you can update documents even using just doc-values (without
stored). While I understand the columnar-format, my issue with this is that
docValues are added when a 'commit' is done (right?). Does that mean that
it will force a commit (which is a slow operation) when updating with
docValu
: I am using solr 4.2, and have set up spatial search config as below
:
: http://wiki.apache.org/solr/SpatialSearch#Schema_Configuration
:
: But everything I make an update to a document,
: http://wiki.apache.org/solr/UpdateJSON#Updating_a_Solr_Index_with_JSON
:
: more values of the *_coordinat
Hi
I am using solr 4.2, and have set up spatial search config as below
http://wiki.apache.org/solr/SpatialSearch#Schema_Configuration
But everything I make an update to a document,
http://wiki.apache.org/solr/UpdateJSON#Updating_a_Solr_Index_with_JSON
more values of the *_coordinates fields get
On Fri, Jul 13, 2012 at 3:50 PM, Jonatan Fournier
wrote:
> On Thu, Jul 12, 2012 at 3:20 PM, Jonatan Fournier
> wrote:
> But later on when I want to "append" cat3 to the field by doing this:
>
> "mv_f":{"add":"cat3"},
> ...
>
> I end up with something like this in the index:
>
> "mv_f":["{add=cat3
On Thu, Jul 12, 2012 at 3:20 PM, Jonatan Fournier
wrote:
> Yonik,
>
> On Thu, Jul 12, 2012 at 12:52 PM, Yonik Seeley
> wrote:
>> On Thu, Jul 12, 2012 at 12:38 PM, Jonatan Fournier
>> wrote:
>>> On Thu, Jul 12, 2012 at 11:05 AM, Erick Erickson
The partial documents update that Jonatan refere
>> I've just committed this change.
>
> Super thanks! I assume it will end up in the 4.0 release?
Yep!
-Yonik
http://lucidimagination.com
On Fri, Jul 13, 2012 at 1:43 PM, Yonik Seeley
wrote:
> On Fri, Jul 13, 2012 at 1:41 PM, Jonatan Fournier
> wrote:
>> On Fri, Jul 13, 2012 at 12:57 AM, Yonik Seeley
>> wrote:
>>> On Thu, Jul 12, 2012 at 3:20 PM, Jonatan Fournier
>>> wrote:
Is there a flag for: if document does not exist, cr
On Fri, Jul 13, 2012 at 1:41 PM, Jonatan Fournier
wrote:
> On Fri, Jul 13, 2012 at 12:57 AM, Yonik Seeley
> wrote:
>> On Thu, Jul 12, 2012 at 3:20 PM, Jonatan Fournier
>> wrote:
>>> Is there a flag for: if document does not exist, create it for me?
>>
>> Not currently, but it certainly makes sen
On Fri, Jul 13, 2012 at 12:57 AM, Yonik Seeley
wrote:
> On Thu, Jul 12, 2012 at 3:20 PM, Jonatan Fournier
> wrote:
>> Is there a flag for: if document does not exist, create it for me?
>
> Not currently, but it certainly makes sense.
> The implementation should be easy. The most difficult part is
On Thu, Jul 12, 2012 at 3:20 PM, Jonatan Fournier
wrote:
> Is there a flag for: if document does not exist, create it for me?
Not currently, but it certainly makes sense.
The implementation should be easy. The most difficult part is figuring
out the best syntax to specify this.
Another idea: we
Yonik,
On Thu, Jul 12, 2012 at 12:52 PM, Yonik Seeley
wrote:
> On Thu, Jul 12, 2012 at 12:38 PM, Jonatan Fournier
> wrote:
>> On Thu, Jul 12, 2012 at 11:05 AM, Erick Erickson
>>> The partial documents update that Jonatan references also requires
>>> that all the fields be stored.
>>
>> If my onl
On Thu, Jul 12, 2012 at 12:38 PM, Jonatan Fournier
wrote:
> On Thu, Jul 12, 2012 at 11:05 AM, Erick Erickson
>> The partial documents update that Jonatan references also requires
>> that all the fields be stored.
>
> If my only fields with stored="false" are copyField (e.g. I don't need
> their co
Erick,
On Thu, Jul 12, 2012 at 11:05 AM, Erick Erickson
wrote:
> Vinicius:
>
> No, fetching the document from the index, changing selected values and
> re-indexing probably
> won't work at all. The problem is that you only get _stored_ values
> back from Solr. So unless
> you've specified 'stored
Vinicius:
No, fetching the document from the index, changing selected values and
re-indexing probably
won't work at all. The problem is that you only get _stored_ values
back from Solr. So unless
you've specified 'stored="true" ' for all your fields, you can't use
the doc fetched from Solr to
upda
On Wed, Jul 11, 2012 at 10:57 AM, Vinicius Carvalho
wrote:
> Hi there.
>
> I was checking the faq and found that solr does not support field updates
> right. So I assume that in order to update a document, one should first
> retrieve it by its Id and then change the required field and update the d
Document size should not have any impact on deleting document as they are only
marked for deletion.
On Tuesday 30 August 2011 17:06:05 Jeff Leedy wrote:
> I was curious to know if anyone has any information about the relative
> performance of document updates (delete/add operations) on documents
I was curious to know if anyone has any information about the relative
performance of document updates (delete/add operations) on documents
of different sizes. I have a use case in which I can either create
large Solr documents first and subsequently add a small amount of
information to them, or do
Hi Adeel,
As far as I know, this isn't possible yet, but some work is being done:
https://issues.apache.org/jira/browse/SOLR-139
https://issues.apache.org/jira/browse/SOLR-828
Regards,
*Juan*
On Thu, Jul 7, 2011 at 2:24 PM, Adeel Qureshi wrote:
> What I am trying to do is to update a docume
What I am trying to do is to update a document information while keeping
data for the fields that arent being specified in the update.
So e.g. if this is the schema
123
some title
active
if i send
123
closed
it should update the status to be closed for this document but not wipe out
title
This is being worked on for Solr 1.4:
https://issues.apache.org/jira/browse/SOLR-139
Bill
On Wed, Oct 15, 2008 at 7:47 PM, Walter Underwood <[EMAIL PROTECTED]>wrote:
> Neither Solr no Lucene support partial updates. "Update" means
> "add or replace". --wunder
>
> On 10/15/08 4:23 PM, "[EMAIL PR
Neither Solr no Lucene support partial updates. "Update" means
"add or replace". --wunder
On 10/15/08 4:23 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Hi,
> I've been trying to find a way to post partial updates, updating only
> some of the fields in a set of records, via POSTed XM
Hi,
I've been trying to find a way to post partial updates, updating only
some of the fields in a set of records, via POSTed XML messages to a solr
1.3.0 index. In the wiki (http://wiki.apache.org/solr/UpdateXmlMessages),
it almost seems like there's a special root tag which isn't
mentioned
document.Please,I hope any
suggestion!!!
For example,something like this:
SOLR1000
9
Regards..
--
View this message in context:
http://www.nabble.com/Updating-documents-in-Solr-tp16742850p16742850.html
Sent from the Solr - User mailing list archive at Nabble.com.
34 matches
Mail list logo
