lZYR8PZh8Bv7qIrMUB65eapI_JnE&r=lUsTzFRk0CX38HvagQ0wd52D67dA0fx_D6M6F3LHzAU&m=46aWsPOdFln3UfXqa4uKg7kfgMDRN4sPY-mHbsuWcTs&s=ZiW2uFD77PXO_3ZCczSQ4DAY5O_dOSYy5pUOpOBRFjI&e=
" -jar post.jar
/tmp/solr_data/data
I don't see the post.jar in Solr 7.2 anymore, it is just "post", n
I remember there is a post.jar in Cloudera's Solr (very old version) that
allows indexing doc like:
java -Dtype=application/json -Drecursive -Durl="
http://localhost:8983/solr/indexer_odac/update/json/docs"; -jar post.jar
/tmp/solr_data/data
I don't see the post.jar in Sol
Jan
Thanks for your help, I’m going recommend to my team to upgrade, we’re not in
production yet so it shouldn’t be an issue.
Sent from my iPhone
> On Sep 14, 2019, at 9:00 AM, Jan Høydahl wrote:
>
> JWT auth is not backported to 7.x and also requires changes to other core
> parts of Solr.
JWT auth is not backported to 7.x and also requires changes to other core parts
of Solr. So just dropping in the jars will not work.
I’d encourage you to upgrade to 8.x
Jan Høydahl
> 13. sep. 2019 kl. 19:54 skrev Tyrone Tse :
>
> I only copied the 2 jars
>
> -
>
> jwt-auth-1.0.0.jar
>
>
I only copied the 2 jars
-
jwt-auth-1.0.0.jar
-
jose4j-0.6.3.jar
to the $SOLR_HOME/lib folder, to install the code for the
https://github.com/cominvent/solr-auth-jwt plugin
On Fri, Sep 13, 2019 at 11:55 AM Shawn Heisey wrote:
> On 9/13/2019 10:30 AM, Tyrone Tse wrote:
> > When
On 9/13/2019 10:30 AM, Tyrone Tse wrote:
When I check the solr.log file I am seeing the following error
2019-09-13 15:09:27.816 ERROR (main) [ ] o.a.s.s.SolrDispatchFilter Could
not start Solr. Check solr/home property and the logs
2019-09-13 15:09:27.838 ERROR (main) [ ] o.a.s.c.SolrCore
nu
I am testing the JWT Auth plugin from
https://github.com/cominvent/solr-auth-jwt
as my project is using Solr 7.2.
I downloaded the master branch for the code, and I built the
jwt-auth-1.0.0.jar
with the mvn package command.
I then copied the jar to my $SOLR_HOME/lib/
I also downloaded the
;uf=query&df=edismax
>>
>> But this only result in q being allowed through, but not parsed - i.e.:
>> "+(+DisjunctionMaxQuery(((synrank80:tagmytagingeniør)^8.0 |
>> (stemrank40:tagmytagingeniør)^4.0…
>>
>> Does anybody have any experience or tips for enabling tagging of queries
>> for SOLR >= 7.2?
>>
>> Regards
>>
>> Fredrik
result in q being allowed through, but not parsed - i.e.:
> "+(+DisjunctionMaxQuery(((synrank80:tagmytagingeniør)^8.0 |
> (stemrank40:tagmytagingeniør)^4.0…
>
> Does anybody have any experience or tips for enabling tagging of queries
> for SOLR >= 7.2?
>
> Regards
>
> Fredrik
wed through, but not parsed - i.e.:
"+(+DisjunctionMaxQuery(((synrank80:tagmytagingeniør)^8.0 |
(stemrank40:tagmytagingeniør)^4.0…
Does anybody have any experience or tips for enabling tagging of queries for
SOLR >= 7.2?
Regards
Fredrik
Hello, I am working on a project implementing Zookeeper and Solr cloud on a
cluster with 3 servers. I need to secure my zookeeper nodes so that they can
only communicate among themselves, I tried implementing ACLs according to the
documentation
(https://lucene.apache.org/solr/guide/7_2/zookee
uniqueBlock is not faster than BlockJoinFacet in 7.4.
On Tue, Aug 7, 2018 at 8:05 AM Aditya Gandhi wrote:
> I'm querying an Index which has two types of child documents (let's call
> them ChildTypeA and ChildTypeB)
> I wrap the subqueries for each of these documents in a boolean clause,
> somet
I'm querying an Index which has two types of child documents (let's call
them ChildTypeA and ChildTypeB)
I wrap the subqueries for each of these documents in a boolean clause,
something like this:
*q=+{! parent which=type:parent } +{! parent
which=type:parent }*
I've been trying to get facet cou
I THINK this might be a bug? I've had troubles with how the Solr Managed
Synonym endpoint handles URL encoding of synonyms. It seems to be
impossible to delete a synonym which has a forward slash in it.
I have a synonym with a key of "Hot/Cold Pack" (that's the key that shows
up when I GET the man
Thank you Shawn & Edwin. It was a certificate error. I did not have the IPs
list in the SAN in the format required for IPs. After I updated the SAN
list, I was able to run the ADDREPLICA API correctly.
-Antony
On Thu, Apr 12, 2018 at 10:20 PM, Shawn Heisey wrote:
> On 4/12/2018 9:48 PM, Antony
On 4/12/2018 9:48 PM, Antony A wrote:
Thank you. I was trying to create the collection using the API.
Unfortunately the API changes a bit between 6x to 7x.
I posted the API that I used to create the collection and subsequently when
trying to create cores for the same collection.
https://pastebi
Hi Edwin,
Thank you. I was trying to create the collection using the API.
Unfortunately the API changes a bit between 6x to 7x.
I posted the API that I used to create the collection and subsequently when
trying to create cores for the same collection.
https://pastebin.com/hrydZktX
Hopefully thi
Hi,
I can't really catch what is the issue you are facing.
Regards,
Edwin
On 13 April 2018 at 04:06, Antony A wrote:
> Hi,
>
> I am trying to add a replica to the ssl-enabled solr cloud with external
> zookeeper ensemble.
>
> 2018-04-12 18:26:29.140 INFO (qtp672320506-51) [ ]
> o.a.s.h.a.C
Hi,
I am trying to add a replica to the ssl-enabled solr cloud with external
zookeeper ensemble.
2018-04-12 18:26:29.140 INFO (qtp672320506-51) [ ]
o.a.s.h.a.CollectionsHandler Invoked Collection Action :addreplica with
params
node=_solr&action=ADDREPLICA&collection=collection_name&shard=sha
Wow life is complicated :)
Since I am using this to start solr, I am assuming the one in
/server/scripts/cloud-scripts is being used:
./bin/solr start -cloud -s /usr/local/bin/solr-7.2.1/server/solr/node1/solr
-p 8983 -z zk0-esohad:2181,zk1-esohad:2181,zk5-esohad:2181 -m 10g
So, I guess I need to
Technically, Solr doesn't name the file at all, that's in your log4j
config, this line:
log4j.appender.file.File=${solr.log}/solr.log
so it's weird that you can't find it on your machine at all. How do
you _start_ Solr? In particular, to you define a system variable
"-Dsolr.log=some_path"?
And a
Not located in the /server/logs/ folder.
Have these files instead
solr-8983-console.log
solr_gc.log.0.current
I can see logs from the Solr dashboard. Where is the solr.log file going
to? A search of "solr.log" in the system did not find the file.
Is the file called something else for solrcloud
On 3/29/2018 12:45 PM, Abhi Basu wrote:
> Also, another question, where it says to copy the zoo.cfg from
> /solr72/server/solr folder to /solr72/server/solr/node1/solr, should I
> actually be grabbing the zoo.cfg from one of my external zk nodes?
If you're using zookeeper processes that are separa
Just an update. Adding hostnames to solr.xml and using "-z
zk1:2181,zk2:2181,zk3:2181" worked and I can see 4 live nodes and able to
create collection with 2S/2R.
Thanks for your help, greatly appreciate it.
Regards,
Abhi
On Thu, Mar 29, 2018 at 1:45 PM, Abhi Basu <9000r...@gmail.com> wrote:
>
Also, another question, where it says to copy the zoo.cfg from
/solr72/server/solr folder to /solr72/server/solr/node1/solr, should I
actually be grabbing the zoo.cfg from one of my external zk nodes?
Thanks,
Abhi
On Thu, Mar 29, 2018 at 1:04 PM, Abhi Basu <9000r...@gmail.com> wrote:
> Ok, will
Ok, will give it a try along with the host name.
On Thu, Mar 29, 2018 at 12:20 PM, Webster Homer
wrote:
> This Zookeeper ensemble doesn't look right.
> >
> > ./bin/solr start -cloud -s /usr/local/bin/solr-7.2.1/server/solr/node1/
> -p
> > 8983 -z zk0-esohad,zk1-esohad,zk3-esohad:2181 -m 8g
>
>
This Zookeeper ensemble doesn't look right.
>
> ./bin/solr start -cloud -s /usr/local/bin/solr-7.2.1/server/solr/node1/ -p
> 8983 -z zk0-esohad,zk1-esohad,zk3-esohad:2181 -m 8g
Shouldn't the zookeeper ensemble be specified as:
zk0-esohad:2181,zk1-esohad:2181,zk3-esohad:2181
You should put the
I had that problem. Very annoying and we probably should require special flag
to use localhost.
We need to start solr like this:
./solr start -c -h `hostname`
If anybody ever forgets, we get a 127.0.0.1 node that shows down in cluster
status. No idea how to get rid of that.
wunder
Walter Unde
So, in the solr.xml on each node should I set the host to the actual host
name?
${host:}
${jetty.port:8983}
${hostContext:solr}
${genericCoreNodeNames:true}
${zkClientTimeout:3}
${distribUpdateSoTimeout:60}
${distribUpdateConnTimeout:6}
${zkCrede
On 3/29/2018 8:25 AM, Abhi Basu wrote:
"Operation create caused
exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
Cannot create collection ems-collection. Value of maxShardsPerNode is 1,
and the number of nodes currently live or live and part of your
I'm be
Yes, only showing one live node on admin site.
Checking zk logs.
Thanks,
Abhi
On Thu, Mar 29, 2018 at 9:32 AM, Ganesh Sethuraman
wrote:
> may be you can check int he Admin UI --> Cloud --> Tree --> /live_nodes. To
> see the list of live nodes before running. If it is less than what you
> expe
may be you can check int he Admin UI --> Cloud --> Tree --> /live_nodes. To
see the list of live nodes before running. If it is less than what you
expected, check the Zoo keeper logs? or make sure connectivity between the
shards and zookeeper.
On Thu, Mar 29, 2018 at 10:25 AM, Abhi Basu <9000r...@
What am I missing? I used the following instructions
http://blog.thedigitalgroup.com/susheelk/2015/08/03/solrcloud-2-nodes-solr-1-node-zk-setup/#comment-4321
on 4 nodes. The only difference is I have 3 external zk servers. So this
is how I am starting each solr node:
./bin/solr start -cloud -s /u
Please ignore this. It was a user error. I was pointing to the wrong
analyzer in my app's cfg file.
Steve
On Mon, Mar 26, 2018 at 10:17 AM, Steven White wrote:
> Setting "sow=true" didn't make a difference.
>
> Here is what I'm using now: http://localhost:8983/
> solr/ccfts/select_test?q=%22r
Setting "sow=true" didn't make a difference.
Here is what I'm using now:
http://localhost:8983/solr/ccfts/select_test?q=%22record%20type%20session%22&wt=json&indent=true&sow=true&debugQuery=true
And here is the output:
{
"responseHeader":{
"status":0,
"QTime":1,
"params":{
"q
Hello, Steven.
Have you tried sow=true?
see
https://lucene.apache.org/solr/guide/7_2/the-extended-dismax-query-parser.html
Anyway, you can start from debugQuery=true, then try to explore
explainOther, and get to Analysis page after all.
On Mon, Mar 26, 2018 at 3:10 AM, Steven White wrote:
> H
Hi everyone,
I switched over from Solr 5.2.1 to 7.2.1 other than re-indexing my data and
schema design remain the same.
The issue I see now is I'm getting 0 hits on phrase searches, why?
Here is the query I'm sending that gives me 0 hits:
http://localhost:8983/solr/ccfts/select_test?q=%22cat+do
Hi,
In the Solr 7.2 JSON API, when faceting over terms, I would like to sort
the buckets over the average of a numerical property, as shown below
curl http://localhost:8983/solr/core/select -d '
q=*:*&
rows=0&
wt=json&
json.facet={
"field" : {
Hi,
What is the Tesseract OCR version that comes with Solr 7.2.0?
I can't manage to locate the information in the documentation.
Thanks.
Regards,
Edwin
ariusz Wojtas
>
>
> On Fri, Dec 29, 2017 at 10:57 AM, Diego Ceccarelli (BLOOMBERG/ LONDON) <
> dceccarel...@bloomberg.net> wrote:
>
>> Dariusz, does the rerank query work?
>>
>> From: solr-user@lucene.apache.org At: 12/28/17 22:25:28To:
>> solr-user@lucene.apac
LONDON) <
dceccarel...@bloomberg.net> wrote:
> Dariusz, does the rerank query work?
>
> From: solr-user@lucene.apache.org At: 12/28/17 22:25:28To:
> solr-user@lucene.apache.org
> Subject: Re: SOLR 7.2 and LTR
>
> Yes, this could be SOLR-11501.
> But from the description
Dariusz, does the rerank query work?
From: solr-user@lucene.apache.org At: 12/28/17 22:25:28To:
solr-user@lucene.apache.org
Subject: Re: SOLR 7.2 and LTR
Yes, this could be SOLR-11501.
But from the description in the ticket I see no option to run LTR, unless I
am missing something.
I have
berg.net> wrote:
> From a (very) quick look it seems like the https://issues.apache.org/
> jira/browse/SOLR-11501 upgrade notes might be relevant, potentially.
>
> From: solr-user@lucene.apache.org At: 12/28/17 15:18:22To:
> solr-user@lucene.apache.org
> Subject: Re: SOLR 7.2
From a (very) quick look it seems like the
https://issues.apache.org/jira/browse/SOLR-11501 upgrade notes might be
relevant, potentially.
From: solr-user@lucene.apache.org At: 12/28/17 15:18:22To:
solr-user@lucene.apache.org
Subject: Re: SOLR 7.2 and LTR
Do you have the ltr qparser plugin
/17 13:58:26To:
solr-user@lucene.apache.org
Subject: Re: SOLR 7.2 and LTR
Hello Diego,
solr.log contains always the same single stacktrace in SOLR 7.2.
I've been trying to pass rq via solrconfig.xml and via HTTP form.
The /searchIncidents handler contains edismax query.
Works if I compl
Hello Diego,
solr.log contains always the same single stacktrace in SOLR 7.2.
I've been trying to pass rq via solrconfig.xml and via HTTP form.
The /searchIncidents handler contains edismax query.
Works if I completely disable rq. When I add the rq param, even something
like:
{!ltr reRan
Hi,
I am using SOLR 7.0 and use the ltr parser.
The configuration I use works nicely under SOLR 7.0.0.
I am trying to upgrade to 7.2.0 but whenever I want to use my handler, I
get an exception:
"rq parameter must be a RankQuery"
The exact response is:
org.apache.solr.common.SolrException
org.ap
47 matches
Mail list logo
