Are they stored=true?
On Thu, Jun 11, 2020, 10:14 Dongtao wrote:
> I have a Solr atomic json update job running successfully for adding values
> on specific fields, but two fields description/keywords (i am using Nutch
> web crawler) contents are dropped after json atomic update. Could not
> fi
I have a Solr atomic json update job running successfully for adding values
on specific fields, but two fields description/keywords (i am using Nutch
web crawler) contents are dropped after json atomic update. Could not
figure out why
Any helps are appreciated.
--
Sent from: https://lucene.472
he.org
Subject: Re: Solr Atomic update change value and field name
Try adding -format solr to your bin/post command. By default the post command
will treat input as arbitrary json, not solr-format json.
Jan Høydahl
> 21. mai 2020 kl. 02:50 skrev Hup Chen :
>
> I am new to Solr. I tried to d
Try adding -format solr to your bin/post command. By default the post command
will treat input as arbitrary json, not solr-format json.
Jan Høydahl
> 21. mai 2020 kl. 02:50 skrev Hup Chen :
>
> I am new to Solr. I tried to do Atomic update by using .json file update.
> $SOLR/bin/post not only
I am new to Solr. I tried to do Atomic update by using .json file update.
$SOLR/bin/post not only changing field values, but field name also has become
"fieldname.set", for instance, "price" become "price.set". Update by curl
/update handler was working well but since I have several millions of
Hi Doss,
What was existing value and what happens after you do atomic update?
Kind Regards,
Furkan KAMACI
On Wed, Jul 24, 2019 at 2:47 PM Doss wrote:
> HI,
>
> I have a multiValued field of type String.
>
> multiValued="true"/>
>
> I want to keep this list unique, so I am using atomic updates
HI,
I have a multiValued field of type String.
I want to keep this list unique, so I am using atomic updates with
"add-distinct"
{"docid":123456,"namelist":{"add-distinct":["Adam","Jane"]}}
but this is not maintaining the expected uniqueness, am I doing something
wrong? Guide me please.
Than
How are you updating? All the stored stuff is assuming "Atomic Updates"..
On Wed, Mar 8, 2017 at 11:15 AM, Alexandre Rafalovitch
wrote:
> Uhm, actually, If you have copyField from multiple sources into that
> _text_ field, you may be accumulating/duplicating content on update.
>
> Check what ha
Uhm, actually, If you have copyField from multiple sources into that
_text_ field, you may be accumulating/duplicating content on update.
Check what happens to the content of that _text_ field when you do
full-text and then do an attribute update.
If I am right, you may want to have a separate "o
Guys
A BIG thank you, it works perfectly!!!
After so much research I finally got my solution working.
That was the trick, _text_ is stored and it’s working as expected.
Have a very nice day and thanks a lot for your contribution.
Really appreciated
Nico
> On 8 Mar 2017, at 18:26, Nicolas Boui
Hi Erick, Shawn,
Thx really a lot for your swift reaction, it’s fantastic.
Let me answer both your answers:
1) the df entry in solrconfig.xml has not been changed:
_text_
2)when I do a query for full-text search I don’t specify a field, I just enter
the string I’m looking for in the q paramete
bq: I wonder if it won’t be simpler for me to write a custom handler
Probably not, that would be Java too ;)...
OK, back up a bit. You can change your schema such that the full-text
field _is_ stored, I don't quite know what the default field is from
memory, but you must be searching against it ;
On 3/8/2017 9:22 AM, Nicolas Bouillon wrote:
> - I checked in the schema, all the fields that matter (Tika default
> extracted fields) and my customer fields are stored=true. - I suppose
> that the full-text index is not stored in a field? And
When you do a full text query, what field/fields are
Hi Erick
Thanks a lot for the elaborated answer. Let me give some precisions:
1. I upload the docs using an AJAX post multiform to my server.
2. The PHP target of the post, takes the file and stores it on disk
3. If the file is moved successfully from TEMP files to final destination, I
then call
Nico:
This is the place for such questions! I'm not quite sure the source
of the docs. When you say you "extract", does that mean you're using
the ExtractingRequestHandler, i.e. uploading PDF or Word etc. to Solr
and letting Tika parse it out? IOW, where is the fulltext coming from?
For adding t
Dear SOLR friends,
I developed a small ERP. I produce PDF documents linked to objects in my ERP:
invoices, timesheets, contracts, etc...
I have also the possibility to attach documents to a particular object and when
I view an invoice for instance, I can see the attached documents.
Until now, I
on this?
>
>
> Begin forwarded message:
>
>> From: Marcos Mendez
>> Subject: solr atomic update
>> Date: January 31, 2013 7:09:23 AM EST
>> To: solr-user@lucene.apache.org
>>
>> Is there a way to do an atomic update (inc by 1) and retrieve the value in
>> one operation?
>
Any ideas on this?
Begin forwarded message:
> From: Marcos Mendez
> Subject: solr atomic update
> Date: January 31, 2013 7:09:23 AM EST
> To: solr-user@lucene.apache.org
>
> Is there a way to do an atomic update (inc by 1) and retrieve the value in
> one operation?
hi
were you able to do atomic update for specific field using curlim using
curl from windows cmd but getting error like host can not be resolved im
using this command:
C:\Users\rohan>curl www.localhost.com:8983/solr/update?commit=true -H
"Content-t
ype:text/json" -d '[{"value":"samsung-wave-s5
Not that I know of...
Best
Erick
On Thu, Jan 31, 2013 at 7:09 AM, Marcos Mendez wrote:
> Is there a way to do an atomic update (inc by 1) and retrieve the updated
> value in one operation?
Is there a way to do an atomic update (inc by 1) and retrieve the updated value
in one operation?
Just saw this:
https://issues.apache.org/jira/browse/SOLR-4134
so I don't think you can do what you want currently without the patch.
Erick
On Fri, Dec 21, 2012 at 7:58 AM, Erick Erickson wrote:
> Hmmm, looks like it might be a bug, but I don't know that code at all.
> Wonder what Yonik would
Hmmm, looks like it might be a bug, but I don't know that code at all.
Wonder what Yonik would have to say
On Wed, Dec 19, 2012 at 9:52 AM, Dikchant Sahi wrote:
> Hi Erick,
>
> The name field is stored. I experience problem only when I update
> multiValued field with multiple values like,
>
Hi Erick,
The name field is stored. I experience problem only when I update
multiValued field with multiple values like,
* solr*
* lucene*
*
*
It works perfect, when I set single value for multiValued field like,
*solr*
Thanks,
Dikchant
On Wed, Dec 19, 2012 at 6:25 PM, Erick Erickson wrote:
> F
FIrst question: Is the "name" field stored (stored="true")? If it isn't,
that would explain your problems with that field. _all_ relevant fields
(i.e. everything not a destination of a copyField) need to be stored for
atomic updates to work.
Your second problem I'm not sure about. I remember some
Hi,
Does Solr 4.0 allows to update the values of multi-valued field? Say I have
list of values for skills field like java, j2ee and i want to change it
to solr, lucene.
I was trying to play with atomic updates and below is my observation:
I have following document in my index:
1
Dikchant
softwa
26 matches
Mail list logo
