Hi Jim,
Very interesting scenario that we didn't anticipate. I think this is a
limitation of the MoveReplica API which does not move core properties.
But it also raises questions such as whether to always move all core
properties? I personally think core properties are an artifact that was
server is also 7.4
and your assumption/check on null values on input doc seems legit... I have
added some checks before pushing the doc to solr and replaced null values
with some default values, and updates seem going through w/o problem...
though having a little bit explanatory logs on server
On 9/5/2018 8:32 PM, deniz wrote:
I have set up a schemaless solr (cloud) and have been trying to test the
updates. as DIH is not going through field guessing, I have wrote a small
piece of code to query data from db and push the docs to solr...
Once the client pushes the docs to solr, on
Hi Luca,
I wonder if payloads might be able to solve your case for contextual
synonyms?
http://jorgelbg.github.io/posts/solr-contextual-synonyms
Ryan
On Mon, 3 Sep 2018 at 21:59 Andrea Gazzarini wrote:
> Hi Luca,
> I believe this is not an easy task to do passing through Solr/Lucene
>
nope, the data i am pushing is stuff like string, int, etc etc
i have have checked further and made bunch of trial and error, here are the
things I was able to figure out:
- If a date value from database is null, then it is breaking the update
with "-00-00" is not a valid date string error.
Are you trying to push a java hash to solr?
On Sep 5, 2018, at 10:32 PM, deniz
mailto:denizdurmu...@gmail.com>> wrote:
I have set up a schemaless solr (cloud) and have been trying to test the
updates. as DIH is not going through field guessing, I have wrote a small
piece of code to query data
I have set up a schemaless solr (cloud) and have been trying to test the
updates. as DIH is not going through field guessing, I have wrote a small
piece of code to query data from db and push the docs to solr...
Once the client pushes the docs to solr, on server there are npe logs as
below:
Checked git history for TimeSeriesStream on master, and I cannot see any
commits related to this?
SOLR-11914: Deprecated some SolrParams methods. * toSolrParams(nl) moved to a
NamedList method, which is more natural. David Smiley 23.04.2018, 19:26
SOLR-11629: Add new CloudSolrClient.Builder
Hello,
We're creating a SolrCloud in AWS and attempting to use autoscaling to add
replicas during nodeAdded/nodeLost. This was working fine for us until we
started creating collections specifying core properties (e.g.
/solr/admin/collections?action=CREATE_datasource=REDACTED).
It seems that when
On 9/5/2018 11:36 AM, Monique Monteiro wrote:
I need to add a deltaQuery to a DIH configuration, but it should reference
a different datasource. Example:
*
* ...*
Is it possible?
As far as I am aware, each entity can only reference one dataSource.
Both of
Hi all,
I need to add a deltaQuery to a DIH configuration, but it should reference
a different datasource. Example:
*
* ...*
Is it possible?
Thanks in advance.
--
Monique Monteiro
Twitter: http://twitter.com/monilouise
I created SOLR-12743 to track this.
On Mon, Jul 16, 2018 at 12:30 PM Markus Jelsma
wrote:
> Hello Thomas,
>
> To be absolutely sure you suffer from the same problem as one of our
> collections, can you confirm that your Solr cores are leaking a
> SolrIndexSearcher instance on each commit? If
I think this is pretty bad. I created
https://issues.apache.org/jira/browse/SOLR-12743. Feel free to add any more
details you have there.
On Mon, Sep 3, 2018 at 1:50 PM Markus Jelsma
wrote:
> Hello Björn,
>
> Take great care, 7.2.1 cannot read an index written by 7.4.0, so you
> cannot roll
To unsubscribe:
Please follow the instructions here:
http://lucene.apache.org/solr/community.html#mailing-lists-irc. You
must use the _exact_ same e-mail as you used to subscribe.
If the initial try doesn't work and following the suggestions at the
"problems" link doesn't work for you, let us
Here's what I copied from an explanation from Uwe Schindler, 'cause I
believe most anything he has to say on this subject:
It is just simple, Lucene locking and commits do not work correct on
NFS file systems because they are not fully POSIX conformant. Because
of this you may also produce
Jack:
Thanks for letting us know, that provides evidence that will help
prioritize upgrading ZK.
Erick
On Wed, Sep 5, 2018 at 7:15 AM Jack Schlederer
wrote:
>
> Ah, yes. We use ZK 3.4.13 for our ZK server nodes, but we never thought to
> upgrade the ZK JAR within Solr. We included that in our
I have now opened https://issues.apache.org/jira/browse/SOLR-12737 for this.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi,
Can you please clarify "precision" preference definition? For instance, is
freedisk "precision" is honored when comparing the max and the min freedisk
of all nodes in the sortedNodes list? Or is it between any consecutive
nodes in the sortedNodes list? I think it may be the latter but then
Thank you.
On Tue, Sep 4, 2018 at 10:34 PM Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
> The "sortedNodes" shows the nodes in the system from the most loaded to
> least loaded order. All other things being equal, a node having the least
> free disk space will come first and the last
Ah, yes. We use ZK 3.4.13 for our ZK server nodes, but we never thought to
upgrade the ZK JAR within Solr. We included that in our Solr image, and
it's working like a charm, re-resolving DNS names when new ZKs come up with
different IPs. Thanks for the help guys!
--Jack
On Sat, Sep 1, 2018 at
I have tested this with latest released ver 7.4.0
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 4. sep. 2018 kl. 16:32 skrev Joel Bernstein :
>
> Which version are you using?
>
> I remember addressing this issue, but it may have been in Alfresco's
> version of
You're right, my answer forgot to mention the *tokenizerFactory*
parameter that you can add in the filter declaration. But, differently
from what you think the default tokenizer used for parsing the synonyms
_is not_ the tokenizer of the current analyzer (StandardTokenizer in
your example) but
On 9/5/2018 6:55 AM, Imran Rajjad wrote:
I am using Solr Cloud 6.4.1. After a hard restart the solr nodes are
constantly showing to be in DOWN state and would not go into recovery. I
have also deleted the write.lock files from all the replica folders, but
the problem would not go away. The error
Hi Andrea,
thank you for your answer.
About the second question: The standardTokenizer should be applied also
to the phrase query, so the ' and - symbols should be removed even
there, and this should allow a match in the synonim file isn't it?
With an example:
in phrase query:
"Cytosolic
On 9/5/2018 2:55 AM, Sudip Mukherjee wrote:
I have a 2 node SOLR (7.x) cloud cluster on which I have collection with replicas (
replicationFactor = 2, shard = 1 ). I am seeing that the replicas do not come up ( state is
"down") when both nodes are restarted. From the "legend" in Graph
Hello,
I am using Solr Cloud 6.4.1. After a hard restart the solr nodes are
constantly showing to be in DOWN state and would not go into recovery. I
have also deleted the write.lock files from all the replica folders, but
the problem would not go away. The error displayed at web console is : no
Hi,
I am using a custom handler with edismax parser. I am using uf parameter in
the handler to restrict some fields from search. But uf is not working with
post filter(fq). I want to restricted same fields in fq, so that people
could not filter on some fields. Please suggest how can I do that.
Hi,
I am using a custom handler with edismax parser. I am using uf parameter in
the handler to restrict some fields from search. But uf is not working with
post filter(fq). I want to restricted same fields in fq, so that people
could not filter on some fields. Please suggest how can I do that.
Hi Danilo,
let's see if this can help you (I'm sorry for the poor debugging, I'm
reading & writing from my mobile): the first issue should have something
to do with synonym overlapping and since I'm very curious about what it
is happening, I will be more precise when I will be in front of a
Hello to all,
I have an issue related to synonimgraphfilter expanding the wrong
synonims for a phrase-term at query time.
I have a dictionary with the following lines
P49902,Cytosolic purine 5'-nucleotidase,EC 3.1.3.5,Cytosolic 5'-nucleotidase II
A8K9N1,Glucosidase\, beta\, acid
By the way, I am doing this on Solr 7.4.0. Sorry, forgot to include that in
my earlier post.
On Wed, 5 Sep 2018 at 17:39, Zheng Lin Edwin Yeo
wrote:
> Hi,
>
> I am looking at implementing the NeuralNetworkModel for the Solr LTR which
> uses the "pairwise" approach, as it seems to be a better
Hi,
I am looking at implementing the NeuralNetworkModel for the Solr LTR which
uses the "pairwise" approach, as it seems to be a better option than the
LinearModel, which uses the "pointwise" approach..
I am following the setup from the following site:
Hi,
I have a 2 node SOLR (7.x) cloud cluster on which I have collection with
replicas ( replicationFactor = 2, shard = 1 ). I am seeing that the replicas do
not come up ( state is "down") when both nodes are restarted. From the
"legend" in Graph section, I see that the replicas are in
33 matches
Mail list logo
