On 9/12/2015 10:51 AM, Mr Havercamp wrote:
> Unfortunately, has never changed. The issue can take some time
> to show itself although I think there were logic issues with the way I
> update documents in my index.
>
> I first do a full purge and reindex of all items without issue.
>
> Over time,
Unfortunately, has never changed. The issue can take some time
to show itself although I think there were logic issues with the way I
update documents in my index.
I first do a full purge and reindex of all items without issue.
Over time, I only index items that have changed/are new since
Please explain what you're trying to do in more detail. That JIRA
is about splitting existing shards which is slightly different than
adding replicas.
Splitting shards is implemented, but without any additional information
about what you're trying to _do_, it's hard to say anything. You haven't
hi
in my schema i have a tag field.
this field set multiValued="true".
now my question is about search on multivalued field.
if i add thid doc to sor:
{
id:1,
tag:{"tag1","tag2"}
},
{
id:2,
tag:{"tag1","tag2"}
},
when i search on q="tag1"
i get just :
{
id:1,
tag:{"tag1","tag2"}
},
but if i
It seems that you have secured Solr so thoroughly that you cannot now run
bin/solr status!
bin/solr has no arguments as yet for providing a username/password - as a
mostly user like you I'm not sure of the roadmap.
I think you should relax those restrictions a bit and try again.
On Fri, Sep 11,
Hi,
I recently started exploring solrcloud.
While adding a new replica using collection api, I faced an issue as
mentioned in https://issues.apache.org/jira/browse/SOLR-7399
Is there any temp fix for the issue has no comment or solution posted yet.
Best Rgds
Noble,
You should also look at this if it is intended to be more than an internal
API. Using the minor protections I added to test SOLR-8000, I was able to
reproduce a problem very like this:
bin/solr healthcheck -z localhost:2181 -c mycollection
Since Solr /select is protected...
On Sat,
