Re: Verify a certain Replica contains a document

Yes. Here's what I do: Start two embedded Solr nodes (i.e. like using MiniSolrCloudCluster). They were started on ports 63175 and 63201. Create a collection with one shard and replica. /solr/admin/collections?action=clusterstatus shows it was created on 127.0.0.1:63201_solr. Index a document: cu

Re: Verify a certain Replica contains a document

Did you also try querying /core.name/select with distrib=false ? On Fri, May 15, 2015 at 9:22 PM, Shai Erera wrote: > Hi > > Is there a REST API in Solr that allows me to query a certain Replica/core? > I am writing some custom replica-recovery code and I'd like to verify that > it works well. >

Verify a certain Replica contains a document

Hi Is there a REST API in Solr that allows me to query a certain Replica/core? I am writing some custom replica-recovery code and I'd like to verify that it works well. I wanted to use the /collection/select API, passing shards=host.under.test:ip/solr/collection, but that also works even if 'host

JSON

Can we gt this one fixed? If the Body is empty don't through a Null Pointer Exception? Thanks >* >http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=foundation"; ;* >* -H "Content-type:appli

Re: Searcher is opening twice on Reload

Any help here.. With Regards Aman Tandon On Fri, May 15, 2015 at 1:24 PM, Aman Tandon wrote: > Thanks chris, but in the issue it is mentioned that first searcher > listener is opening twice but in my case firstly the firstSearcher is > opening and then newSearcher. Is it same? > > With Regards

Re: schema.xml & xi:include -> copyField source :'_my_title' is not a glob and doesn't match any explicit field or dynamicField

Hi Clemens, I forgot that XInclude requires well-formed XML, so schema-common.xml without tags won’t work, since it will have multiple root elements. But instead of XInclude, you can define external entities for files you want to include, and then include a reference to them where you want the

Re: Problem with solr.LengthFilterFactory

Sorry that my brain has turned to mush... the issue you are hitting is due to a known, undocumented limit in the whitespace tokenizer: https://issues.apache.org/jira/browse/LUCENE-5785 "White space tokenizer has undocumented limit of 256 characters per token" If you look at the parsed query you w

Re: Problem with solr.LengthFilterFactory

On 5/15/2015 2:06 PM, Charles Sanders wrote: > I have deleted all records from my index. Stopped solr. Made the schema > changes as requested. Started solr. Then insert the one test record. Then > search. Still see the same results. No portal_package is not the unique key, > its uri. Which is a

Re: Problem with solr.LengthFilterFactory

Shawn, Thanks a bunch for working with me on this. I have deleted all records from my index. Stopped solr. Made the schema changes as requested. Started solr. Then insert the one test record. Then search. Still see the same results. No portal_package is not the unique key, its uri. Which is a

Re: Problem with solr.LengthFilterFactory

On 5/15/2015 1:23 PM, Shawn Heisey wrote: > Then I looked back at your fieldType definition and noticed that you > are only defining an index analyzer. Remove the 'type="index"' part of > the analyzer config so it happens at both index and query time, > reindex, then try again. The reindex may be

Re: Problem with solr.LengthFilterFactory

On 5/15/2015 12:47 PM, Charles Sanders wrote: > Ran the same test as below. Added echoParams=all and debug=query. Thanks for > the help! Initially, I was a little confused by something I saw in your debug output. I've broken up the query text with newlines into 50 character increments for clari

Re: Problem with solr.LengthFilterFactory

Ran the same test as below. Added echoParams=all and debug=query. Thanks for the help! Results { "responseHeader": { "status": 0, "QTime": 46, "params": { "spellcheck": "true", "enableElevation": "false", "df": "allText", "echoParams": "all", "spellcheck.maxCollations": "5", "spellch

Re: Problem with solr.LengthFilterFactory

On 5/15/2015 10:04 AM, Charles Sanders wrote: > Agree 100%. The value returned is the value stored. Not affected by the > analyzer. > > However, I searched for that token. See my query? I would expect the analyzer > to remove the large token. So that when I search for the large token I would >

NPE when Faceting with MoreLikeThis handler in Solr 5.1.0

Hi everyone, Recently I upgraded to solr 5.1.0. When trying to generate facets using the more like this handler, I now get a a NullPointerException. I never got this exception while using Solr 4.10.0 Details are below: Stack Trace: at org.apache.solr.request.SimpleFacets.getHeatmapCounts(Simple

Re: Problem with solr.LengthFilterFactory

Agree 100%. The value returned is the value stored. Not affected by the analyzer. However, I searched for that token. See my query? I would expect the analyzer to remove the large token. So that when I search for the large token I would find nothing. Rather it returns my record. Am I missing

Re: Problem with solr.LengthFilterFactory

The returned value is the stored or original source value - only the indexed terms are affected by token filtering. You could use an update processor if you want to adjust the actual source value, such as the truncate processor to truncate long source values: http://lucene.apache.org/solr/5_1_0/s

Re: Solr 5.1 json facets: buckets are empty for TrieIntField

Indeed, it does work in a nightly build. Thank you Yonik On Fri, May 15, 2015 at 5:27 PM, Yonik Seeley wrote: > That was previously found and fixed - can you try a recent nightly build? > > https://builds.apache.org/job/Solr-Artifacts-5.x/lastSuccessfulBuild/artifact/solr/package/ > -Yonik > > >

Re: Problem with solr.LengthFilterFactory

Yes, that is what I am seeing. Looking in the code myself, I see no reason for this behavior. That is why I assumed I was doing something very wrong. Below I have included an example. I set the max length to 300. I insert a record with a single token of 500 characters. I expect the token to be

Re: Solr 5.1 json facets: buckets are empty for TrieIntField

That was previously found and fixed - can you try a recent nightly build? https://builds.apache.org/job/Solr-Artifacts-5.x/lastSuccessfulBuild/artifact/solr/package/ -Yonik On Fri, May 15, 2015 at 4:04 AM, Andrii Berezhynskyi wrote: > I have a strange issue of facet buckets being empty for tint

Re: Problem with solr.LengthFilterFactory

On 5/15/2015 8:49 AM, Charles Sanders wrote: > I'm seeing a problem with the LengthFilter. It appears to work fine until I > increase the max value above 254. At the point it stops removing the very > large token from the stream. As a result I get the error: > java.lang.IllegalArgumentException:

Problem with solr.LengthFilterFactory

I'm seeing a problem with the LengthFilter. It appears to work fine until I increase the max value above 254. At the point it stops removing the very large token from the stream. As a result I get the error: java.lang.IllegalArgumentException: Document contains at least one immense term.. U

Re: how to index and query newly added filed

Images are stripped by the mail server, but I did see the original. Things to check 1> the field must have 'stored="true" ' set 2> you must add documents with that field. 3> Only documents that actually have a value in the field will show anything. Solr doesn't return an empty field, so if a pa

Re: Full Copy during cluster restarts

The most likely cause is that you were indexing when the nodes were down and/or have not issued a hard commit. If you stop indexing _and_ issue a hard commit (openSearcher=true or false doesn't matter), then the nodes should come back up without having to replicate the index. This might help: http

how to index and query newly added filed

Hi,I am new to solr. From this image, i have added one new field 'startPrice'. i am selecting that filed but it is not coming in response. what would be the probme, -- View this message in context: http://lucene.472066.n3.nabble.com/

AW: schema.xml & xi:include -> copyField source :'_my_title' is not a glob and doesn't match any explicit field or dynamicField

Thought about that too (should have written ;) ). When I remove the schema-tag from the composite xml I get: org.apache.solr.common.SolrException: Unable to create core [test] at org.apache.solr.core.CoreContainer.create(CoreContainer.java:533) at org.apache.solr.core.CoreContainer.

Re: schema.xml & xi:include -> copyField source :'_my_title' is not a glob and doesn't match any explicit field or dynamicField

Hi Clemens, I think the problem is the structure of the composite schema - you’ll end up with: <- your other schema file <- the included schema-common.xml tags from your schema-common.xml. You won’t be able to use it alone in that case, but if you need to do that, you could j

Solr 5.1 json facets: buckets are empty for TrieIntField

I have a strange issue of facet buckets being empty for tint fields. I have the following schema: ... Then I just import: [{ "sku": "TEST_FACET", "color": "yellow", "width": 100.23, "price": 1200 }] when I do the following faceting request: json.facet={ colors:{ter

Re: A Synonym Searching for Phrase?

Hi Ryan, I am not really sure whether this[1] solution mentioned in the link below can work for your case considering its cons. However, I recommend having a quick look at it. @Chris, Would eagerly wait for your contribution. [1] https://support.lucidworks.com/hc/en-us/articles/205359448 On

schema.xml & xi:include -> copyField source :'_my_title' is not a glob and doesn't match any explicit field or dynamicField

Given the following schema.xml _my_id When I try to include the very schema from another schema file, e.g.: http://www.w3.org/2001/XInclude"/> I get SolrException copyField source :'_my_title' is not a glob and doesn't match any explicit f

Re: Searcher is opening twice on Reload

Thanks chris, but in the issue it is mentioned that first searcher listener is opening twice but in my case firstly the firstSearcher is opening and then newSearcher. Is it same? With Regards Aman Tandon On Thu, May 14, 2015 at 11:05 PM, Chris Hostetter wrote: > > I suspect you aren't doing any