Issues in Solr-7.3

[tapan1707]

We are planning to upgrade our Solr-6.4 to Solr-7.x. While considering the
appropriate minor version, I saw that there are many ongoing issues for
Solr-7.3 users on the mailing list. 
Just wanted to take an expert opinion if it's *safe* to just upgrade to 7.3
without worrying about creating (or adding) patches for too many issues or
should we go for Solr-7.2 for the time being. 

Thanks in advance.



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Graph traversal: Bypass cycle detection?

[Joel Bernstein]

Hi,

At this time cycle detection is built into the nodes expression and cannot
be turned off. The nodes expression is really designed to do a traditional
breadth first search through a graph where cycle detection is needed so you
don't continually walk the same nodes.

Are you looking to do random walk analysis? I've been meaning to add a
function that supports random walks on a graph that would not do cycle
detection.

Joel Bernstein
http://joelsolr.blogspot.com/

On Wed, Jun 6, 2018 at 9:25 AM, Christian Spitzlay <
christian.spitz...@biologis.com> wrote:

> Hi,
>
> is it possible to bypass the cycle detection so a traversal
> can revisit nodes?
>
> The documentation at
> https://lucene.apache.org/solr/guide/7_3/graph-
> traversal.html#cycle-detection
> does not mention any and lists reasons why the cycle detection is in place.
> But if I were willing to live with the consequences would it be possible?
>
>
> Best regards
> Christian Spitzlay
>
>

solr search connectivity error with shards

[Dinesh Sundaram]

Hi,

I have a domain called test.com to process solr search queries with 2 solr
instances like below. second URL[2] works fine but I dont want to show up
the localhost, portnumber to the end user so I tried to configure like
first URL[1] but it is not working. I have the proxy pass in test.com
apache to redirect /select to /solr. not sure why the second url[2] is
trying to call from my solr server and it is end up with connection timeout
error since test.com is not in the same DMZ network. is there any way to
achieve this externalizer implementation?

NOTE: all the shards URL works individually when it is combined throwing
n/w exception because first query reaching target server, second query is
originated from target server so connection broken.



[1]
https://test.com/select/mediator?fl=id,locale,headline,short_description,record,title,description,url=(locale:en-us+OR+page_locale:en-us)+AND+((offerSearch:*test*)+OR+(content:test))=8=https://test.com/select/global?fl=id,https://test.com/select/test-global?fl=id=start_time+asc=0=json


[2]
https://test.com/select/mediator?fl=id,locale,headline,short_description,record,title,description,url=(locale:en-us+OR+page_locale:en-us)+AND+((offerSearch:*test*)+OR+(content:test))=8=https://localhost:8983/solr/global/select?q=*:*,https://localhost:8983/global/select?q=*:*=start_time+asc=0=json


Caused by: org.apache.solr.client.solrj.SolrServerException: IOException
occured when talking to server at: https://test.com:443/select/test-global
at
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:640)
at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:253)
at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:242)
at
org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1219)
at
org.apache.solr.handler.component.HttpShardHandler.lambda$submit$0(HttpShardHandler.java:172)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:176)
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:188)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)

Re: Error deleting copy field

[Steve Rowe]

Ikenna,

Can you please create a JIRA issue[1], and if possible include your schema?

Thanks.

--
Steve
www.lucidworks.com

[1] 
https://wiki.apache.org/solr/HowToContribute#JIRA_tips_.28our_issue.2Fbug_tracker.29

> On Jun 6, 2018, at 5:16 PM, Ikenna Okonkwo  wrote:
> 
> Hi Steve,
> 
> I didn't use a dynamic field. It was an exact match.
> 
> -- 
> Ikenna Okonkwo
> Senior Front End Developer, WMX Project
> Phone: (905) 821-2111 (Ext: 78847)
> Mobile: (437) 922-9004
> ikenna.okon...@walmart.com
> 
> Walmart Canada Corp.
> 1940 Argentia Road
> Mississauga, Ontario L5N 1P9
> Save money. Live better.
> 
> On 2018-06-06, 5:07 PM, "Steve Rowe"  wrote:
> 
>Hi Ikenna,
> 
>If the source field(s) are dynamic fields, then you have to give the same 
> spelling you used when you created the copy field.  E.g. for ‘item_desc_en’, 
> if the source field in the copy field directive is ‘*_desc_en’, then you have 
> to use that when you issue the delete.
> 
>You can find out the exact spelling of your copy field rules by looking at 
> the schema.
> 
>--
>Steve
>www.lucidworks.com
> 
>> On Jun 6, 2018, at 5:00 PM, Ikenna Okonkwo  
>> wrote:
>> 
>> Hi all,
>> 
>> I encountered an error when using SOLR cloud 7.2.1. I used the UI to add a 
>> bunch of “copy fields” to a field named “_text_”, and now, I can’t delete 
>> the copy fields nor the field.
>> 
>> I get the error message when I attempt to delete a copy field: Copy field 
>> directive not found: 'item_desc_en' -> '_text_'
>> And I get the following when I try to delete the field itself: Can't delete 
>> field '_text_' because it's referred to by at least one copy field directive.
>> 
>> Any pointers would be helpful.
>> 
>> Thanks!
>> 
>> 
>> --
>> Ikenna Okonkwo
>> Senior Front End Developer, WMX Project
>> Phone: (905) 821-2111 (Ext: 78847)
>> ikenna.okon...@walmart.com
>> 
>> Walmart Canada Corp.
>> 1940 Argentia Road
>> Mississauga, Ontario L5N 1P9
>> Save money. Live better.
> 
> 
> 
> 

Re: Error deleting copy field

[Ikenna Okonkwo]

Hi Steve,

I didn't use a dynamic field. It was an exact match.

-- 
Ikenna Okonkwo
Senior Front End Developer, WMX Project
Phone: (905) 821-2111 (Ext: 78847)
Mobile: (437) 922-9004
ikenna.okon...@walmart.com

Walmart Canada Corp.
1940 Argentia Road
Mississauga, Ontario L5N 1P9
Save money. Live better.

On 2018-06-06, 5:07 PM, "Steve Rowe"  wrote:

Hi Ikenna,

If the source field(s) are dynamic fields, then you have to give the same 
spelling you used when you created the copy field.  E.g. for ‘item_desc_en’, if 
the source field in the copy field directive is ‘*_desc_en’, then you have to 
use that when you issue the delete.

You can find out the exact spelling of your copy field rules by looking at 
the schema.

--
Steve
www.lucidworks.com

> On Jun 6, 2018, at 5:00 PM, Ikenna Okonkwo  
wrote:
> 
> Hi all,
> 
> I encountered an error when using SOLR cloud 7.2.1. I used the UI to add 
a bunch of “copy fields” to a field named “_text_”, and now, I can’t delete the 
copy fields nor the field.
> 
> I get the error message when I attempt to delete a copy field: Copy field 
directive not found: 'item_desc_en' -> '_text_'
> And I get the following when I try to delete the field itself: Can't 
delete field '_text_' because it's referred to by at least one copy field 
directive.
> 
> Any pointers would be helpful.
> 
> Thanks!
> 
> 
> --
> Ikenna Okonkwo
> Senior Front End Developer, WMX Project
> Phone: (905) 821-2111 (Ext: 78847)
> ikenna.okon...@walmart.com
> 
> Walmart Canada Corp.
> 1940 Argentia Road
> Mississauga, Ontario L5N 1P9
> Save money. Live better.

Re: Delete then re-add a core

[BlackIce]

One of the issues with the install script is that when its run by any user
other than "solr" and installed into default directories,
is that one might get ownership/permission problems.

The easiest way to avoid these is by creating the "solr" user BEFORE
installing Solr as a regular "Login-User",
and then install Solr while being logged into this account (Or sudo, etc..)
and then install Solr with NON default values for directories,
have everything installed within the "Solr" users home directory space,
that way everything belongs to the solr user, it is then easily modified,
by just logging into the solr account and one doesn't have to worry
about ownership/permissions.. ad if one makes a mistake it only affects
the "solr" user...

Ayway, just my 2 cents

On Wed, Jun 6, 2018 at 9:41 PM, Amanda Shuman 
wrote:

> Thanks, I was able to do most of the but didn't reinstall... Still running
> into an issue I think is related to current working directory. I guess
> reinstalling might fix that?
> Amanda
>
> On Wed, Jun 6, 2018, 17:27 Erick Erickson  wrote:
>
> > Assuming this is stand-alone:
> > > find the data dir for the core (parent of the index dir)
> > > find the config dir for the core
> > > shut down Solr
> > > "rm -rf data"
> > > make any changes to the configs you want
> > > start Solr
> >
> > As BlackIce said, reinstalling works too.
> >
> > If it's SolrCloud delete and recreate the collection, your configs
> > will be in ZooKeeper. Of course update your configs with your changes
> > before creating the new collection.
> >
> > Best,
> > Erick
> >
> >
> > On Wed, Jun 6, 2018 at 7:09 AM, BlackIce  wrote:
> > > I'm not a Solr guru
> > >
> > > I take i that you installed Solr with the install script
> > > then it installs into a dir where normal users have no right to access
> > the
> > > necessary files...
> > >
> > > One way to circumvent this is to un-install Solr and then re-install
> > > without using the default and have it install into a directory where
> the
> > > solr and login user have access to.
> > >
> > > Deleting a Core is a simple as deleting its directory...
> > >
> > > Hope this helps - good luck
> > >
> > > On Wed, Jun 6, 2018 at 3:59 PM, Amanda Shuman  >
> > > wrote:
> > >
> > >> Oh, and I also have a related question - how can I change my CWD
> > (current
> > >> working directory)? It is set for the /opt/ folder and not /var/ and I
> > >> think that's screwing things up...
> > >> Thanks!
> > >> Amanda
> > >>
> > >> --
> > >> Dr. Amanda Shuman
> > >> Post-doc researcher, University of Freiburg, The Maoist Legacy Project
> > >> 
> > >> PhD, University of California, Santa Cruz
> > >> http://www.amandashuman.net/
> > >> http://www.prchistoryresources.org/
> > >> Office: +49 (0) 761 203 4925
> > >>
> > >>
> > >> On Wed, Jun 6, 2018 at 3:35 PM, Amanda Shuman <
> amanda.shu...@gmail.com>
> > >> wrote:
> > >>
> > >> > Hi all, I'm a bit of a newbie still but have clearly screwed
> something
> > >> > up... so I think what I need to do now is to delete a core (saving
> > >> current
> > >> > conf files as-is) then re-add/re-create the core and re-index. (It's
> > not
> > >> a
> > >> > big site and it's not public yet, so I'm not concerned about taking
> > >> > anything down during this process.)
> > >> >
> > >> > So what's the quickest way to do this:
> > >> >
> > >> > 1. Create a new core at command line with different name, move all
> > conf
> > >> > files into that (?)
> > >> > 2. Delete the current core at command line, but what's the script
> for
> > >> > doing that to make sure it's totally gone? I see different responses
> > >> > online... not sure what's the "best practice" for this...
> > >> >
> > >> > Thanks!
> > >> > Amanda
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > Dr. Amanda Shuman
> > >> > Post-doc researcher, University of Freiburg, The Maoist Legacy
> Project
> > >> > 
> > >> > PhD, University of California, Santa Cruz
> > >> > http://www.amandashuman.net/
> > >> > http://www.prchistoryresources.org/
> > >> > Office: +49 (0) 761 203 4925
> > >> >
> > >> >
> > >>
> >
>

Re: Error deleting copy field

[Steve Rowe]

Hi Ikenna,

If the source field(s) are dynamic fields, then you have to give the same 
spelling you used when you created the copy field.  E.g. for ‘item_desc_en’, if 
the source field in the copy field directive is ‘*_desc_en’, then you have to 
use that when you issue the delete.

You can find out the exact spelling of your copy field rules by looking at the 
schema.

--
Steve
www.lucidworks.com

> On Jun 6, 2018, at 5:00 PM, Ikenna Okonkwo  wrote:
> 
> Hi all,
> 
> I encountered an error when using SOLR cloud 7.2.1. I used the UI to add a 
> bunch of “copy fields” to a field named “_text_”, and now, I can’t delete the 
> copy fields nor the field.
> 
> I get the error message when I attempt to delete a copy field: Copy field 
> directive not found: 'item_desc_en' -> '_text_'
> And I get the following when I try to delete the field itself: Can't delete 
> field '_text_' because it's referred to by at least one copy field directive.
> 
> Any pointers would be helpful.
> 
> Thanks!
> 
> 
> --
> Ikenna Okonkwo
> Senior Front End Developer, WMX Project
> Phone: (905) 821-2111 (Ext: 78847)
> ikenna.okon...@walmart.com
> 
> Walmart Canada Corp.
> 1940 Argentia Road
> Mississauga, Ontario L5N 1P9
> Save money. Live better.

Error deleting copy field

[Ikenna Okonkwo]

Hi all,

I encountered an error when using SOLR cloud 7.2.1. I used the UI to add a 
bunch of “copy fields” to a field named “_text_”, and now, I can’t delete the 
copy fields nor the field.

I get the error message when I attempt to delete a copy field: Copy field 
directive not found: 'item_desc_en' -> '_text_'
And I get the following when I try to delete the field itself: Can't delete 
field '_text_' because it's referred to by at least one copy field directive.

Any pointers would be helpful.

Thanks!


--
Ikenna Okonkwo
Senior Front End Developer, WMX Project
Phone: (905) 821-2111 (Ext: 78847)
ikenna.okon...@walmart.com

Walmart Canada Corp.
1940 Argentia Road
Mississauga, Ontario L5N 1P9
Save money. Live better.

Re: Delete then re-add a core

[Amanda Shuman]

Thanks, I was able to do most of the but didn't reinstall... Still running
into an issue I think is related to current working directory. I guess
reinstalling might fix that?
Amanda

On Wed, Jun 6, 2018, 17:27 Erick Erickson  wrote:

> Assuming this is stand-alone:
> > find the data dir for the core (parent of the index dir)
> > find the config dir for the core
> > shut down Solr
> > "rm -rf data"
> > make any changes to the configs you want
> > start Solr
>
> As BlackIce said, reinstalling works too.
>
> If it's SolrCloud delete and recreate the collection, your configs
> will be in ZooKeeper. Of course update your configs with your changes
> before creating the new collection.
>
> Best,
> Erick
>
>
> On Wed, Jun 6, 2018 at 7:09 AM, BlackIce  wrote:
> > I'm not a Solr guru
> >
> > I take i that you installed Solr with the install script
> > then it installs into a dir where normal users have no right to access
> the
> > necessary files...
> >
> > One way to circumvent this is to un-install Solr and then re-install
> > without using the default and have it install into a directory where the
> > solr and login user have access to.
> >
> > Deleting a Core is a simple as deleting its directory...
> >
> > Hope this helps - good luck
> >
> > On Wed, Jun 6, 2018 at 3:59 PM, Amanda Shuman 
> > wrote:
> >
> >> Oh, and I also have a related question - how can I change my CWD
> (current
> >> working directory)? It is set for the /opt/ folder and not /var/ and I
> >> think that's screwing things up...
> >> Thanks!
> >> Amanda
> >>
> >> --
> >> Dr. Amanda Shuman
> >> Post-doc researcher, University of Freiburg, The Maoist Legacy Project
> >> 
> >> PhD, University of California, Santa Cruz
> >> http://www.amandashuman.net/
> >> http://www.prchistoryresources.org/
> >> Office: +49 (0) 761 203 4925
> >>
> >>
> >> On Wed, Jun 6, 2018 at 3:35 PM, Amanda Shuman 
> >> wrote:
> >>
> >> > Hi all, I'm a bit of a newbie still but have clearly screwed something
> >> > up... so I think what I need to do now is to delete a core (saving
> >> current
> >> > conf files as-is) then re-add/re-create the core and re-index. (It's
> not
> >> a
> >> > big site and it's not public yet, so I'm not concerned about taking
> >> > anything down during this process.)
> >> >
> >> > So what's the quickest way to do this:
> >> >
> >> > 1. Create a new core at command line with different name, move all
> conf
> >> > files into that (?)
> >> > 2. Delete the current core at command line, but what's the script for
> >> > doing that to make sure it's totally gone? I see different responses
> >> > online... not sure what's the "best practice" for this...
> >> >
> >> > Thanks!
> >> > Amanda
> >> >
> >> >
> >> >
> >> > --
> >> > Dr. Amanda Shuman
> >> > Post-doc researcher, University of Freiburg, The Maoist Legacy Project
> >> > 
> >> > PhD, University of California, Santa Cruz
> >> > http://www.amandashuman.net/
> >> > http://www.prchistoryresources.org/
> >> > Office: +49 (0) 761 203 4925
> >> >
> >> >
> >>
>

FINAL REMINDER: Apache EU Roadshow 2018 in Berlin next week!

[sharan]

Hello Apache Supporters and Enthusiasts

This is a final reminder that our Apache EU Roadshow will be held in 
Berlin next week on 13th and 14th June 2018. We will have 28 different 
sessions running over 2 days that cover some great topics. So if you are 
interested in Microservices, Internet of Things (IoT), Cloud, Apache 
Tomcat or Apache Http Server then we have something for you.


https://foss-backstage.de/sessions/apache-roadshow

We will be co-located with FOSS Backstage, so if you are interested in 
topics such as incubator, the Apache Way, open source governance, legal, 
trademarks or simply open source communities then there will be 
something there for you too.  You can attend any of talks, presentations 
and workshops from the Apache EU Roadshow or FOSS Backstage.


You can find details of the combined Apache EU Roadshow and FOSS 
Backstage conference schedule below:


https://foss-backstage.de/schedule?day=2018-06-13

Ticket prices go up on 8th June 2018 and we have a last minute discount 
code that anyone can use before the deadline:


15% discount code: ASF15_discount
valid until June 7, 23:55 CET

You can register at the following link:

https://foss-backstage.de/tickets

Our Apache booth and lounge will be open from 11th - 14th June for 
meetups, hacking or to simply relax between sessions. And we will be 
posting regular updates on social media throughout next week so please 
follow us on Twitter @ApacheCon


Thank you for your continued support and we look forward to seeing you 
in Berlin!


Thanks
Sharan Foga, VP Apache Community Development

http://apachecon.com/

PLEASE NOTE: You are receiving this message because you are subscribed 
to a user@ or dev@ list of one or more Apache Software Foundation projects.

Re: BlendedInfixSuggester wiki errata corrige

[Alessandro Benedetti]

Hi Cassandra,
thanks for your reply.
I did the fix in the official documentation as part of the bugfix I am
working on:

LUCENE-8343 
 

Any feedback is welcome !

Cheers






-
---
Alessandro Benedetti
Search Consultant, R Software Engineer, Director
Sease Ltd. - www.sease.io
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Solr Default query parser

[Shawn Heisey]

On 6/6/2018 9:52 AM, Kamal Kishore Aggarwal wrote:
>> What is the default query parser (QP) for solr.
>>
>> While I was reading about this, I came across two links which looks
>> ambiguous to me. It's not clear to me whether Standard is the default QP or
>> Lucene is the default QP or they are same. Below is the screenshot and
>> links which are confusing me.

The default query parser in Solr has the name "lucene".  This query
parser, which is part of Solr, deals with Lucene query syntax.

The most recent documentation states this clearly right after the table
of contents:

https://lucene.apache.org/solr/guide/7_3/the-standard-query-parser.html

It is highly unlikely that the 6.6 documentation will receive any
changes, unless serious errors are found in it.  The omission of this
piece of information will not be seen as a serious error.

Thanks,
Shawn

Re: Solr Default query parser

[Kamal Kishore Aggarwal]

[Correcting the subject]

On Wed, Jun 6, 2018 at 2:37 PM, Kamal Kishore Aggarwal <
kkroyal@gmail.com> wrote:

> Hi Guys,
>
> What is the default query parser (QP) for solr.
>
> While I was reading about this, I came across two links which looks
> ambiguous to me. It's not clear to me whether Standard is the default QP or
> Lucene is the default QP or they are same. Below is the screenshot and
> links which are confusing me.
>
> https://lucene.apache.org/solr/guide/6_6/the-standard-query-parser.html
>
> https://lucene.apache.org/solr/guide/6_6/common-query-parameters.html
>
> Please suggest. Thanks in advance.
>
>
> Regards
> Kamal Kishore
>

Re: Solr Swap space

[JDISTim]

Thank you for this information!
I am working on a client PC where Solr Admin showed 11.64 GB/13.03 GB Swap
Space, and was losing my mind trying to track down the issue!



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Delete then re-add a core

[Erick Erickson]

Assuming this is stand-alone:
> find the data dir for the core (parent of the index dir)
> find the config dir for the core
> shut down Solr
> "rm -rf data"
> make any changes to the configs you want
> start Solr

As BlackIce said, reinstalling works too.

If it's SolrCloud delete and recreate the collection, your configs
will be in ZooKeeper. Of course update your configs with your changes
before creating the new collection.

Best,
Erick


On Wed, Jun 6, 2018 at 7:09 AM, BlackIce  wrote:
> I'm not a Solr guru
>
> I take i that you installed Solr with the install script
> then it installs into a dir where normal users have no right to access the
> necessary files...
>
> One way to circumvent this is to un-install Solr and then re-install
> without using the default and have it install into a directory where the
> solr and login user have access to.
>
> Deleting a Core is a simple as deleting its directory...
>
> Hope this helps - good luck
>
> On Wed, Jun 6, 2018 at 3:59 PM, Amanda Shuman 
> wrote:
>
>> Oh, and I also have a related question - how can I change my CWD (current
>> working directory)? It is set for the /opt/ folder and not /var/ and I
>> think that's screwing things up...
>> Thanks!
>> Amanda
>>
>> --
>> Dr. Amanda Shuman
>> Post-doc researcher, University of Freiburg, The Maoist Legacy Project
>> 
>> PhD, University of California, Santa Cruz
>> http://www.amandashuman.net/
>> http://www.prchistoryresources.org/
>> Office: +49 (0) 761 203 4925
>>
>>
>> On Wed, Jun 6, 2018 at 3:35 PM, Amanda Shuman 
>> wrote:
>>
>> > Hi all, I'm a bit of a newbie still but have clearly screwed something
>> > up... so I think what I need to do now is to delete a core (saving
>> current
>> > conf files as-is) then re-add/re-create the core and re-index. (It's not
>> a
>> > big site and it's not public yet, so I'm not concerned about taking
>> > anything down during this process.)
>> >
>> > So what's the quickest way to do this:
>> >
>> > 1. Create a new core at command line with different name, move all conf
>> > files into that (?)
>> > 2. Delete the current core at command line, but what's the script for
>> > doing that to make sure it's totally gone? I see different responses
>> > online... not sure what's the "best practice" for this...
>> >
>> > Thanks!
>> > Amanda
>> >
>> >
>> >
>> > --
>> > Dr. Amanda Shuman
>> > Post-doc researcher, University of Freiburg, The Maoist Legacy Project
>> > 
>> > PhD, University of California, Santa Cruz
>> > http://www.amandashuman.net/
>> > http://www.prchistoryresources.org/
>> > Office: +49 (0) 761 203 4925
>> >
>> >
>>

SolrJ and autoscaling

[Hendrik Haddorp]

Hi,

I'm trying to read and modify the autoscaling config. The API on 
https://lucene.apache.org/solr/guide/7_3/solrcloud-autoscaling-api.html 
does only mention the REST API. The read part does however also work via 
SolrJ:


    cloudSolrClient.getZkStateReader().getAutoScalingConfig()

Just for the write part I could not find anything in the API. Is this 
still a gap?


regards,
Hendrik

Re: Delete then re-add a core

[BlackIce]

I'm not a Solr guru

I take i that you installed Solr with the install script
then it installs into a dir where normal users have no right to access the
necessary files...

One way to circumvent this is to un-install Solr and then re-install
without using the default and have it install into a directory where the
solr and login user have access to.

Deleting a Core is a simple as deleting its directory...

Hope this helps - good luck

On Wed, Jun 6, 2018 at 3:59 PM, Amanda Shuman 
wrote:

> Oh, and I also have a related question - how can I change my CWD (current
> working directory)? It is set for the /opt/ folder and not /var/ and I
> think that's screwing things up...
> Thanks!
> Amanda
>
> --
> Dr. Amanda Shuman
> Post-doc researcher, University of Freiburg, The Maoist Legacy Project
> 
> PhD, University of California, Santa Cruz
> http://www.amandashuman.net/
> http://www.prchistoryresources.org/
> Office: +49 (0) 761 203 4925
>
>
> On Wed, Jun 6, 2018 at 3:35 PM, Amanda Shuman 
> wrote:
>
> > Hi all, I'm a bit of a newbie still but have clearly screwed something
> > up... so I think what I need to do now is to delete a core (saving
> current
> > conf files as-is) then re-add/re-create the core and re-index. (It's not
> a
> > big site and it's not public yet, so I'm not concerned about taking
> > anything down during this process.)
> >
> > So what's the quickest way to do this:
> >
> > 1. Create a new core at command line with different name, move all conf
> > files into that (?)
> > 2. Delete the current core at command line, but what's the script for
> > doing that to make sure it's totally gone? I see different responses
> > online... not sure what's the "best practice" for this...
> >
> > Thanks!
> > Amanda
> >
> >
> >
> > --
> > Dr. Amanda Shuman
> > Post-doc researcher, University of Freiburg, The Maoist Legacy Project
> > 
> > PhD, University of California, Santa Cruz
> > http://www.amandashuman.net/
> > http://www.prchistoryresources.org/
> > Office: +49 (0) 761 203 4925
> >
> >
>

Re: Delete then re-add a core

[Amanda Shuman]

Oh, and I also have a related question - how can I change my CWD (current
working directory)? It is set for the /opt/ folder and not /var/ and I
think that's screwing things up...
Thanks!
Amanda

--
Dr. Amanda Shuman
Post-doc researcher, University of Freiburg, The Maoist Legacy Project

PhD, University of California, Santa Cruz
http://www.amandashuman.net/
http://www.prchistoryresources.org/
Office: +49 (0) 761 203 4925


On Wed, Jun 6, 2018 at 3:35 PM, Amanda Shuman 
wrote:

> Hi all, I'm a bit of a newbie still but have clearly screwed something
> up... so I think what I need to do now is to delete a core (saving current
> conf files as-is) then re-add/re-create the core and re-index. (It's not a
> big site and it's not public yet, so I'm not concerned about taking
> anything down during this process.)
>
> So what's the quickest way to do this:
>
> 1. Create a new core at command line with different name, move all conf
> files into that (?)
> 2. Delete the current core at command line, but what's the script for
> doing that to make sure it's totally gone? I see different responses
> online... not sure what's the "best practice" for this...
>
> Thanks!
> Amanda
>
>
>
> --
> Dr. Amanda Shuman
> Post-doc researcher, University of Freiburg, The Maoist Legacy Project
> 
> PhD, University of California, Santa Cruz
> http://www.amandashuman.net/
> http://www.prchistoryresources.org/
> Office: +49 (0) 761 203 4925
>
>

Re: BlendedInfixSuggester wiki errata corrige

[Cassandra Targett]

Solr's documentation is now integrated with Lucene/Solr source code, so can
be edited by anyone who is willing or able to submit a patch for it. In
your case, you could integrate these edits with the code changes you're
making for the JIRA issues you reference and include them with the patches
you're working on. I would be happy to review your suggested edits as part
of those patches - I can give you feedback on the doc changes while
ignoring the code changes, which in this case I know nothing about.

If I may, could I suggest we not call Solr's official documentation a
"wiki"? It used to be a wiki, 5 years ago, and then we shifted to a wiki
platform without the wiki features, but since last year it's really not a
wiki at all - it's not a collaborative platform and it's not open for
anyone to edit. It's just the documentation, with edits made via commits to
Lucene/Solr source code in the same way as any code change.

- Cassandra

On Tue, Jun 5, 2018 at 10:06 AM Alessandro Benedetti 
wrote:

> Errata corrige to my Errata corrige post :
>
> e.g.
>
> Position Of First match =   *0 |  1  | 2  | 3 |*
> Linear |1 | 0.9|0.8|0.7
> Reciprocal   |1 | 1/2|1/3|1/4
> Exponential Reciprocal |1 | 1/4|*1/9*|1/16
>
>
>
> -
> ---
> Alessandro Benedetti
> Search Consultant, R Software Engineer, Director
> Sease Ltd. - www.sease.io
> --
> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
>

Delete then re-add a core

[Amanda Shuman]

Hi all, I'm a bit of a newbie still but have clearly screwed something
up... so I think what I need to do now is to delete a core (saving current
conf files as-is) then re-add/re-create the core and re-index. (It's not a
big site and it's not public yet, so I'm not concerned about taking
anything down during this process.)

So what's the quickest way to do this:

1. Create a new core at command line with different name, move all conf
files into that (?)
2. Delete the current core at command line, but what's the script for doing
that to make sure it's totally gone? I see different responses online...
not sure what's the "best practice" for this...

Thanks!
Amanda



--
Dr. Amanda Shuman
Post-doc researcher, University of Freiburg, The Maoist Legacy Project

PhD, University of California, Santa Cruz
http://www.amandashuman.net/
http://www.prchistoryresources.org/
Office: +49 (0) 761 203 4925

Graph traversal: Bypass cycle detection?

[Christian Spitzlay]

Hi,

is it possible to bypass the cycle detection so a traversal 
can revisit nodes?

The documentation at
https://lucene.apache.org/solr/guide/7_3/graph-traversal.html#cycle-detection
does not mention any and lists reasons why the cycle detection is in place.
But if I were willing to live with the consequences would it be possible?


Best regards
Christian Spitzlay

Re: Apache and Apache Solr together

[Andrea Gazzarini]

Hi,
all what you need is in Solr, better: all what you need is Solr.

Solr is a server which exposes its services through HTTP, so you don't 
need Apache at all (at least for a training course).


Best,
Andrea

On 06/06/18 08:57, azharuddin wrote:

I've got a question: I came across  Apache Solr
   as requirement for a module
I'm installing and even after reading the documentation on Apache Solr's
official homepage I'm still not sure whether Apache runs alongside regular
Apache or does it require it own server? If it does work alongside Apache,
is there any known issues/problems that I should be aware of? How would this
architecture (Apache and Apache Solr) in terms of file system and serving
pages? I'm sorry if the question might sound silly but I'm very new to the
whole server-side programming/setup world.



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Apache and Apache Solr together

[azharuddin]

I've got a question: I came across  Apache Solr
   as requirement for a module
I'm installing and even after reading the documentation on Apache Solr's
official homepage I'm still not sure whether Apache runs alongside regular
Apache or does it require it own server? If it does work alongside Apache,
is there any known issues/problems that I should be aware of? How would this
architecture (Apache and Apache Solr) in terms of file system and serving
pages? I'm sorry if the question might sound silly but I'm very new to the
whole server-side programming/setup world.



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Windows monitoring software for Solr recommendation

[azharuddin]

Visit here to get more information on  Apache SOLR
  .



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Sole Default query parser

[Kamal Kishore Aggarwal]

Hi Guys,

What is the default query parser (QP) for solr.

While I was reading about this, I came across two links which looks
ambiguous to me. It's not clear to me whether Standard is the default QP or
Lucene is the default QP or they are same. Below is the screenshot and
links which are confusing me.

https://lucene.apache.org/solr/guide/6_6/the-standard-query-parser.html

https://lucene.apache.org/solr/guide/6_6/common-query-parameters.html

Please suggest. Thanks in advance.


Regards
Kamal Kishore

Streaming Expression intersect() behaviour

[Christian Spitzlay]

Hi,

I don’t seem to get the behaviour of the intersect() stream decorator.
I only ever get one doc from the left stream when I would have expected 
more than one.

I constructed a test case that does not depend on my concrete index:

intersect(
cartesianProduct(tuple(fieldA=array(c,c,a,b,d,d)), fieldA, productSort="fieldA 
asc"),
cartesianProduct(tuple(fieldB=array(c,c,a,d,d)), fieldB, productSort="fieldB 
asc"),
on="fieldA=fieldB“
)


The result:

{
  "result-set": {
"docs": [
  {
"fieldA": "a"
  },
  {
"EOF": true,
"RESPONSE_TIME": 0
  }
]
  }
}


I would have expected all the docs from the left stream with fieldA values a, 
c, d
and only the docs with fieldA == b missing.  Do I have a fundamental 
misunderstanding?


Best regards
Christian Spitzlay

Re: sharding guidelines

[Emir Arnautović]

In case you missed, following blog posts might come handy:

https://lucidworks.com/2012/07/23/sizing-hardware-in-the-abstract-why-we-dont-have-a-definitive-answer/
 

http://www.od-bits.com/2018/01/solrelasticsearch-capacity-planning.html 


HTH,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/



> On 6 Jun 2018, at 00:12, Shawn Heisey  wrote:
> 
> On 6/4/2018 4:36 PM, Oakley, Craig (NIH/NLM/NCBI) [C] wrote:
>> We have a collection (one shard, two replicas, currently running Solr6.6) 
>> which sometimes becomes unresponsive on the non-leader node. It is 214 
>> gigabytes, and we were wondering whether there is a rule of thumb how large 
>> to allow a core to grow before sharding. I have a reference in my notes from 
>> the 2015 Solr conference in Austin "baseline no more than 100 million 
>> docs/shard" and "ideal shard-to-memory ratio, if at all possible index 
>> should fit into RAM, but other than that it gets really specific really 
>> fast"; but that was several versions ago, and so I wanted to ask whether 
>> these suggestions have been recalculated.
> 
> In a word, no.
> 
> It is impossible to give generic advice.  One person may have very good 
> performance with 300 million docs in a single index.  Another may have 
> terrible performance with half a million docs per shard.  It depends on a lot 
> of things, including but not limited to the specs of the servers you use, 
> exactly what is in your index, how you have configured Solr, and the nature 
> of your queries.
> 
> Thanks,
> Shawn
> 

Re: Block join query parser

[Mikhail Khludnev]

[child] has childFilter param. Also, mind about [subquery]

On Wed, Jun 6, 2018 at 9:33 AM, Ryan Yacyshyn 
wrote:

> Hi all,
>
> I'm looking for a way to query nested documents that would return the
> parent documents along with its child documents nested under it, but only
> the child documents that match the query. The [child] doc transformer comes
> close, but it returns all child docs.
>
> I'm looking for something similar to ES' inner hits (
> https://www.elastic.co/guide/en/elasticsearch/reference/
> current/search-request-inner-hits.html
> ).
>
> Is this possible?
>
> Thanks,
> Ryan
>



-- 
Sincerely yours
Mikhail Khludnev

solr daterange data not match

[Albert Lee]

Hi all,

I defined a date range type in solr schema.
And then I try to write date to solr in my Java code, like this,
SimpleDateFormat sdf = new SimpleDateFormat(“-MM-dd HH:mm:ss”);
doc.addField(“date”,  sdf.parse(“1990-01-01 15:36:42”));

while the data in solr is:
"date": "1900-01-01T08:00:00Z"

Anyone knows why the difference is not 8 hours?

Regards,
Albert

Block join query parser

[Ryan Yacyshyn]

Hi all,

I'm looking for a way to query nested documents that would return the
parent documents along with its child documents nested under it, but only
the child documents that match the query. The [child] doc transformer comes
close, but it returns all child docs.

I'm looking for something similar to ES' inner hits (
https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-inner-hits.html
).

Is this possible?

Thanks,
Ryan

Re: Windows monitoring software for Solr recommendation

[Deepak Goel]

It would be a bit extensive, but would be interesting to know if a similar
error/situation occurs in Linux too (there are kernel level debugging tools
available for this open source OS)

On Wed, 6 Jun 2018, 10:59 Shawn Heisey,  wrote:

> On 6/5/2018 10:26 PM, TK Solr wrote:
> > I visualized the GC log with GCMV (GCVM?) and the graph shows Solr was
> > using less than half of the heap space at the peak.
> > This Solr doesn't get much query traffic and no indexing was running.
> > It's really a sudden death of JVM with no trace.
> >
>
> If you aren't concerned about what you see in a GC analysis, then the
> heap may not be an issue.  FYI, this is where I would have sent the log
> once I got it:
>
> http://gceasy.io/
>
> This website does a VERY good job of detecting possible problems with
> the heap and GC.
>
> > The only concern I have is that the Solr config files are that of Solr
> > 5.x and they just upgraded to Solr 6.6. But I understand Solr 6
> > supports Solr 5 compatible mode. Has there been any issue in the
> > compatibility mode?
>
> If the config was actually *designed* for 5.x, then it should have
> little problem working in 6.x.  If it was designed for an earlier
> version and just happened to work in 5.x, then I would be less
> optimistic about it working in 6.x.  That said ... it is very unlikely
> that anything in the index config files would cause crashes, even if
> there is a compatibility problem.
>
> The simple truth is that most Java software, including Solr, just
> doesn't ever crash unless there's something VERY wrong.
>
> Actual crashes do happen in the wild, they're just very rare.  Extremely
> severe memory starvation at the OS level can cause problems where
> processes die without any logging, or the OS kills them explicitly.  If
> the java heap is properly sized for the system, that shouldn't be
> possible.  Since you're running Solr 6, you're running Java 8 minimum.
> PermGen is gone in Java 8.  Similar issues to what used to happen with
> PermGen can still happen with the new piece called Metaspace, but if the
> overall system config is good, that shouldn't be a problem.
>
> Thanks,
> Shawn
>
>