Thanks a lot. Appreciate the pointers about indexing engine vs database .
I ended up using concatenating the fields to generate a key.
On Wed, Apr 24, 2019 at 11:39 AM David Hastings <
hastings.recurs...@gmail.com> wrote:
> another thing to consider doing is just merge the two fields into the
Hey Shawn,
Thanks for the response. I was using 3.5.3-beta and after your suggestion I
tried 3.5.4-beta as well as the latest 3.4.* Zookeeper with the same issue.
Trying to execute the mntr command directly revealed the problem because I got
an error message that said that the mntr command
another thing to consider doing is just merge the two fields into the id
value:
"id": "USER_RECORD_12334",
since its a string.
On Wed, Apr 24, 2019 at 2:35 PM Gus Heck wrote:
> Hi Vivek
>
> Solr is not a database, nor should one try to use it as such. You'll need
> to adjust your thinking
Hi Vivek
Solr is not a database, nor should one try to use it as such. You'll need
to adjust your thinking some in order to make good use of Solr. In Solr
there is normally an id field and it should be unique across EVERY document
in the entire collection. Thus there's no concept of a primary
There’s some documentation in the ref guide, did you see it?
Basically, if a replica is discovered by a solr instance by finding a
“core.properties” file under SOLR_HOME, legacyCloud=true will try to
reconstruct the ZooKeeper entry if it’s not there. This lead to lots of issues,
and so it has
What is legacyCloud properties does. Is there a document I could refer. Why
it impacts collection creation with rule based and index copy from one to
another. Replicas not registered how to fix without legacyCloud=true
settings.
--
Sent from:
Hi Shawn, Mikhail
Any suggestions/pointers for using zipper algorithm. I'm facing below error.
Thanks and Regards,
Srinivas Kashyap
**
From: Srinivas Kashyap
Sent: 12 April 2019 03:10 PM
To:
This fix has also been backported to Solr 6.6.6 for users who are
stuck with Solr 6.x.
(Sorry, I hadn't updated the issue and hence this was missed in the
original mail.)
On Wed, Apr 24, 2019 at 12:35 PM Noble Paul wrote:
>
> CVE-2018-11802: Apache Solr authorization bug disclosure
> Severity:
Forwarding to solr-user list
> Videresendt melding:
>
> Fra: Noble Paul
> Emne: CVE-2018-11802: Apache Solr authorization bug vulnerability disclosure
> Dato: 24. april 2019 kl. 09:04:55 CEST
> Til: Lucene Dev , java-u...@lucene.apache.org,
> secur...@apache.org,
Hi,
Is there any way to reference the 'val' value of a bucket in the JSON
facet API? I have a set of records that all have collection tags. I want
to facet on those collections and sort them by a function that uses the
number of search documents in that collection and the total number of
Hi Ashis,
Short answer: No, i don't think it's possible.
I'm considering as well extending solr to allow plugging in features from
outside, but it will require time because at the moment the features can
see only the current document processed, while to do that ideally you want
to process in one
Hi ,
Hope you are doing well!!!
I am currently trying to implement Learn To Rank in SOLR 7.5. I have gone
through the blogs and documentation page to follow the steps. However the
current process looks like i need to write SOLR query in a json file to
upload the same to Feature Store.
But the
Hi,
I am using the below JSON Facet to retrieve the count of all the different
collections in one query.
13 matches
Mail list logo
