Please check doc's unique key(Id). All keys shd be unique. Else docs having
same id will be replaced.
On 04-Sep-2016 12:13 PM, "Ganesh M" wrote:
> Hi,
> we are keep sending documents to Solr from our app server. Single document
> per request, but in parallel of 10 request hits solr cloud in a se
Nitin, Thanks for reply. Our each document has unique id and its hbase rowkey
id. So it will be unique only. So there is no chance of duplicates id being
send.
On Sun 4 Sep, 2016 12:41 pm Nitin Kumar,
mailto:nitinkumar.i...@gmail.com>> wrote:
Please check doc's unique key(Id). All keys shd be
Thanks a lot alex.
The issue was because as u said it did not match the definition
:-)
On 4 Sep 2016 8:35 a.m., "Alexandre Rafalovitch [via Lucene]" <
ml-node+s472066n4294558...@n3.nabble.com> wrote:
It should show up in the Admin UI, even if it matches the dynamic
field. So, I would focus o
Hi KRIS,
I noticed three issue with your schema.xml as follows:
1. enablePositionIncrements is not a valid option, please remove it from
all StopFilter defination.
2. invalid multivalued="true" attribute to "text_general" fieldType, remove
it.
3. Two fields metatag.description and metatag.keywords
Hi,
I'm using function query to query on range using sum function.
{!frange l=0 u=100} sum(Field1,Ffield2)
this is working well. However, I'm not able to have the document not in the
range. I've tested
NOT({!frange l=0 u=100} sum(Field1,Ffield2)) but it's not working.
Do you have any idea to do i
I can get this to:
"q":"(+${parent_match} +${condition_match}) {!child
of=${parent_match}}${condition_match}",
"parent_match":"type:release",
"condition_match":"release_name:\"6.1.0\"",
But I am not sure that's "smarter".
Regards,
Alex.
Newsletter and resources for Solr beginners and
Some more information on this... Most of documents get indexed properly. Few
documents are not getting indexed.
All documents POST are seen in the localhost_access and 200 OK response is seen
in local host access file. But in catalina, there are some difference in the
logs for which are indexin
Can you identify the specific documents that 'fail'? What happens if
you post them manually? Try posting them manually but with one field
super-distinct to see whether it made it in. What happens if you post
it to an empty index (copy definition and try).
Also, what's your request handler's parame
Hi Alex,
We tried to post the same manually from SOLR ADMIN / documents UI. It got
indexed successfully. We are sure that it's not duplicate issue. We are
using default update handler and doesn't configure for custom one. We fire
the request to index using direct HTTP request using XML
format. W
Can you try this:
1. Add the document
2. Follow up by optimize in the core admin ui,
If above works then you may need to check your commit.
Regards,
Dheerendra
On Sun, Sep 4, 2016 at 10:47 PM, Ganesh M
wrote:
> Hi Alex,
> We tried to post the same manually from SOLR ADMIN / documents UI. It g
Looks interesting.
I especially like "we analyze it" and then "we analyze/space-split it
again" as the last tutorial example.
Regards,
Alex.
P.s. Cool enough for http://solr.cool/ ?
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/
On 2 September
I can't tell anything from the document provided. So, here would be my thoughts:
If what you see is some sort of concurrency issues, the documents
missed/dropped would unlikely be exactly the same ones. So, if you see
the same documents dropped, it is much more likely to be something to
do with do
12 matches
Mail list logo
