Re: Get handler not working

2017-04-18 Thread PeterCiuffetti
is not the same as the routing key. And then this causes the CloudMLTQParser to issue the message "Error completing MLT request. Could not fetch document with id [/x/]" -- View this message in context: http://lucene.472066.n3.nabble.com/Get-handler-not-working-tp4325130p4330485.html Sent fro

Re: Get handler not working

2017-03-17 Thread Chris Ulicny
I didn't realize extra parameters were ignored on collection creation. I believe I have all of the trace log from the get request included in the attached document. The collection used was setup as CollectionOne previously. One instance in cloud mode with 2 shards with router.field=iqroutingkey.

Re: Get handler not working

2017-03-16 Thread Alexandre Rafalovitch
Well, only router.field is the valid parameter as per https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-CREATE:CreateaCollection In the second case the parameter is ignored and the uniqueKey is used instead, which is different for you. But it is the first case that

Re: Get handler not working

2017-03-16 Thread Chris Ulicny
I think I've figured out where the issue is, at least superficially. It's in what parameter is used to define the field to route on. I set up two collections to use the same configset but slightly altered calls to the Collections API. action=CREATE=CollectionOne=2=compositeId& *router.field*

Re: Get handler not working

2017-03-16 Thread Yonik Seeley
Ah, yeah, if you're using a different route field it's highly likely that's the issue. I was always against that "feature", and this thread demonstrates part of the problem (complicating clients, including us human clients trying to make sense of what's going on). -Yonik On Thu, Mar 16, 2017 at

Re: Get handler not working

2017-03-16 Thread Chris Ulicny
Speaking of routing, I realized I completely forgot to add the routing setup to the test cloud, so it probably has something to do with the issue. I'll add that in and report back. So the routing and uniqueKey setup is as follows: Schema setup: iqdocid I don't think it's mentioned in the

Re: Get handler not working

2017-03-16 Thread Alexandre Rafalovitch
Does real time get implementation reroutes the request internally to a different shard? If not, then maybe the request is going to a non-primary shard. Regards, Alex. http://www.solr-start.com/ - Resources for Solr users, new and experienced On 16 March 2017 at 09:33, Yonik Seeley

Re: Get handler not working

2017-03-16 Thread David Hastings
i still would like to see an experiment where you change the field to id instead of iqdocid, On Thu, Mar 16, 2017 at 9:33 AM, Yonik Seeley wrote: > Something to do with routing perhaps? (the mapping of ids to shards, > by default is based on hashes of the id) > -Yonik > > >

Re: Get handler not working

2017-03-16 Thread Yonik Seeley
Something to do with routing perhaps? (the mapping of ids to shards, by default is based on hashes of the id) -Yonik On Thu, Mar 16, 2017 at 9:16 AM, Chris Ulicny wrote: > iqdocid is already set to be the uniqueKey value. > > I tried reindexing a few documents back into the

Re: Get handler not working

2017-03-16 Thread Alexandre Rafalovitch
If you have the test bed, could you just enable full trace log mode and run two most similar tests. Then look for log difference. It sounds like a bug, but of what kind...? Regards, Alex On 16 Mar 2017 9:16 AM, "Chris Ulicny" wrote: > iqdocid is already set to be the

Re: Get handler not working

2017-03-16 Thread Chris Ulicny
iqdocid is already set to be the uniqueKey value. I tried reindexing a few documents back into the problematic cloud and am getting the same behavior of no document found for get handler. I've also done some testing on standalone instances as well as some quick cloud setups (with embedded zk),

Re: Get handler not working

2017-03-15 Thread Erick Erickson
Wait... Is iqdocid set to the in your schema? That might be the missing thing. On Wed, Mar 15, 2017 at 11:20 AM, Chris Ulicny wrote: > Unless the behavior's changed on the way to version 6.3.0, the get handler > used to use whatever field is set to be the uniqueKey. We have

Re: Get handler not working

2017-03-15 Thread Chris Ulicny
Unless the behavior's changed on the way to version 6.3.0, the get handler used to use whatever field is set to be the uniqueKey. We have successfully been using get on a 4.9.0 standalone core with no explicit "id" field defined by passing in the value for the uniqueKey field to the get handler.

Re: Get handler not working

2017-03-15 Thread David Hastings
if im not mistaken, the real time get handler uses the "id" field exclusively. I have never seen examples that use a different field then that one. the idea behind it is its a solr given unique value, yonik kind of sheds light on it here: http://yonik.com/solr/realtime-get/ so why not use the

Re: Get handler not working

2017-03-15 Thread Alexandre Rafalovitch
What type is your iqdocid? If totally stuck, I would take a non-SolrCloud basic example, index your single document into it and seeing if the problem still exist. Then try to find the mid-point between your config and this config and see if problem is still there. Regards, Alex.

Re: Get handler not working

2017-03-15 Thread David Hastings
from your previous email: "There is no "id" field defined in the schema." you need an id field to use the get handler On Wed, Mar 15, 2017 at 1:45 PM, Chris Ulicny wrote: > I thought that "id" and "ids" were fixed parameters for the get handler, > but I never remember, so

Re: Get handler not working

2017-03-15 Thread Chris Ulicny
I thought that "id" and "ids" were fixed parameters for the get handler, but I never remember, so I've already tried both. Each time it comes back with the same response of no document. On Wed, Mar 15, 2017 at 1:31 PM Alexandre Rafalovitch wrote: > Actually. > > I think

Re: Get handler not working

2017-03-15 Thread Alexandre Rafalovitch
Actually. I think Real Time Get handler has "id" as a magical parameter, not as a field name. It maps to the real id field via the uniqueKey definition: https://cwiki.apache.org/confluence/display/solr/RealTime+Get So, if you have not, could you try the way you originally wrote it. Regards,

Re: Get handler not working

2017-03-15 Thread Chris Ulicny
Sorry, that is a typo. The get is using the iqdocid field. There is no "id" field defined in the schema. solr/TestCollection/get?iqdocid=2957-TV-201604141900 solr/TestCollection/select?q=*:*=iqdocid:2957-TV-201604141900 On Wed, Mar 15, 2017 at 1:15 PM Erick Erickson

Re: Get handler not working

2017-03-15 Thread Erick Erickson
Is this a typo or are you trying to use get with an "id" field and your filter query uses "iqdocid"? Best, Erick On Wed, Mar 15, 2017 at 8:31 AM, Chris Ulicny wrote: > Yes, we're using a fixed schema with the iqdocid field set as the uniqueKey. > > On Wed, Mar 15, 2017 at

Re: Get handler not working

2017-03-15 Thread Chris Ulicny
Yes, we're using a fixed schema with the iqdocid field set as the uniqueKey. On Wed, Mar 15, 2017 at 11:28 AM Alexandre Rafalovitch wrote: > What is your uniqueKey? Is it iqdocid? > > Regards, >Alex. > > http://www.solr-start.com/ - Resources for Solr users, new and

Re: Get handler not working

2017-03-15 Thread Alexandre Rafalovitch
What is your uniqueKey? Is it iqdocid? Regards, Alex. http://www.solr-start.com/ - Resources for Solr users, new and experienced On 15 March 2017 at 11:24, Chris Ulicny wrote: > Hi, > > I've been trying to use the get handler for a new solr cloud collection we > are

Get handler not working

2017-03-15 Thread Chris Ulicny
Hi, I've been trying to use the get handler for a new solr cloud collection we are using, and something seems to be amiss. We are running 6.3.0, so we did not explicitly define the request handler in the solrconfig since it's supposed to be implicitly defined. We also have the update log enabled