It looks like something in your query analyzer chain is turning the
wildcard operators '*' into the word 'star' - maybe you need to dig into
your analyzers, synonym lists etc. and see where this is happening. The
admin/analysis panel that Erick suggests lets you enter data and see
what happens
Dear all,
Although there is no trace of join functionality in the official Solr
documentation
(https://lucene.apache.org/solr/guide/7_4/parallel-sql-interface.html),
joining in parallel sql works in practice. It only works if the field is
not a multivalued field. For my project it would be
Hi Furkan,
I'm using solr 8.3.1 (with openjdk version "11.0.7"), with the following
cache settings:
Thanks
Reinaldo
On Thu, Jun 25, 2020 at 7:45 PM Furkan KAMACI
wrote:
> Hi Reinaldo,
>
> Which version of Solr do you use and could you share your cache settings?
>
>
Hi,
CDCR might be deprecated really soon now --> In this case will it be there any
alternate to this.
However, if this turns out to be not supported or a bug, then we can file a
JIRA issue. --> it will be great if you raise the JIRA ticket for it. So that
we will be more clear that how
Hi Reinaldo,
Which version of Solr do you use and could you share your cache settings?
On the other hand, did you check here:
https://cwiki.apache.org/confluence/display/SOLR/SolrPerformanceProblems
Kind Regards,
Furkan KAMACI
On Thu, Jun 25, 2020 at 11:09 PM Odysci wrote:
> Hi,
>
> I have a
Hello, Vincenzo.
Please find above about a dedicated component doing nothing, but just
holding a config.
Also you may extract config into a file and load it by
SolrResourceLoaderAware.
On Thu, Jun 25, 2020 at 2:06 PM Vincenzo D'Amore wrote:
> Hi Mikhail, yup, I was trying to avoid putting logic
Hi,
I have a solrcloud setup with 12GB heap and I've been trying to optimize it
to avoid OOM errors. My index has about 30million docs and about 80GB
total, 2 shards, 2 replicas.
In my testing setup I submit multiple queries to solr (same node),
sequentially, and with no overlap between the
I observed the exactly same thing - the metrics for only one node.
Looking for the solution to get the metrics of all the nodes.
Could anyone advice?
Thanks,
Chien
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
If I modify the query like this:
{!parent which='class:instruction'}class:observation
It still returns a result for the instruction document, even though the
document with class instruction does not have any children...
Tor-Magne Stien Hagen
-Original Message-
From: Mikhail Khludnev
Hi,
You can also change the multiplication factor in TF IDF snipped in the
source code to 1 also. I know there would be a better method to handle
stopwords now that you have used constant scoring but I wanted to mention
my method by what we got rid of TF.
On Thu, 25 Jun 2020 at 03:02, dbourassa
Hi Community,
This is what I want to achieve:
Suppose that we have 3 locations (name, type, population):
1) Rajasthan, State, -1
2) Udaipur, City, 451K
3) Udaipura, City, 13K
For a search query that will yield all three of these in the result, I want
the result to be ordered the same as
Ok. My fault. Old sport, you know. When retrieving intermediate scopes,
parents bitmask shout include all enclosing scopes as well. It's a dark
side of the BJQ.
{!parent which=`class:(section OR composition)`}
I'm not sure what you try to achieve specifying grandchildren as a
parent-bitmask.
Thanks Jason. Appreciate your response.
Thanks
Fiz N.
On Thu, Jun 25, 2020 at 5:42 AM Jason Gerlowski
wrote:
> Hi Fiz,
>
> Since you're just looking for a POC solution, I think Solr's
> "bin/post" tool would probably help you achieve your first
> requirement.
>
> But I don't think "bin/post"
Hi,
1. Solr is relying on PKI for the request (one cluster sends PKI header to the
node in the other cluster)
-- > I have not configured anything explicitly. Just followed the steps mention
@https://lucene.apache.org/solr/guide/8_4/cdcr-config.html. Is there any
additional step ?
2. That
Hi Aliaksandr
This sounds like a bug to me - I can't think of any reason why this
would be intentional behavior. Maybe I'm missing something and this
is "expected", but if so someone will come along and correct me.
Can you file a JIRA ticket with this information in it?
Jason
On Wed, Jun 24,
I’m mostly trying to identify whether what you are trying to to is a supported
option at all, or of perhaps CDCR is only tested without authentication in
place.
You would also be interested in the fact that CDCR might be deprecated really
soon now, see
Hi Fiz,
Since you're just looking for a POC solution, I think Solr's
"bin/post" tool would probably help you achieve your first
requirement.
But I don't think "bin/post" gives you much control over the fields
that get indexed - if you need the file path to be stored, you might
be better off
Are both clusters setup with the same Identity Provider, so the same JWT token
would be valid for both clusters?
If so, it should be (theoretically) possible to have the clusters talk to each
other, if you can get them to forward the Authorization header with the JWT.
Whoever is sending calls
Hi Mikhail, yup, I was trying to avoid putting logic in Solr.
Just to be a little bit more specific, consider that if the update factory
writes a field that has a size of 50.
The QParser should be aware of the current size when writing a query.
Is it possible to have in solrconfig.xml file a
Sorry, there is no forwardCredentials parameter for JWT, it is implicit.
But from the response we can see two things:
1. Solr is relying on PKI for the request (one cluster sends PKI header to the
node in the other cluster)
2. That fails since the sending node is unknown to the receiving node
Whoever is sending calls to /solr/express_shard1_replica_n3/cdcr will have to
make sure to forward JWT -- How do I forward JWT from source to target server ??
You could try 'forwardCredentials:true' in security.json -- How can I try this
?
Can you suggest me sample security.json which will
Can I get some traction on to this??
--Yaswanth
On Wed, Jun 24, 2020 at 2:18 PM yaswanth kumar
wrote:
> Thanks Erick,
>
> I have now added =query and found a diff between old solr and new
> solr
>
> new solr (8.2) which is not giving results is as follows
>
> "debug":{
>
22 matches
Mail list logo