Solr cloud connectivity issue - Reg

Hi Team, I'm currently working for the solr development project, where we have a development region named https://abc.com. we have deployed solr search engine in tomcat server with port 9000. Also the ssl configuration made in Catalina.properties file in tomcat. i.e., key store file path and key

Re: Mistake assert tips in FST builder ？

The Lucene list is probably better for this question. I'd try java-u...@lucene.apache.org On Mon, Apr 15, 2019 at 9:04 PM zhenyuan wei wrote: > Hi， >With current newest version, 9.0.0-snapshot，In > Builder.UnCompileNode.addArc() function， > found this line： > > assert numArcs == 0 || label

Re: solr 7.x sql query returns null

Do you have multiple shards (including replicas) on the same host for the collection in question? Do the number of shards per host change on the export/index? Kevin Risden On Thu, Apr 18, 2019, 20:50 Joel Bernstein wrote: > That stack trace points here: > >

Re: solr 7.x sql query returns null

That stack trace points here: https://github.com/apache/lucene-solr/blob/releases/lucene-solr/7.3.0/solr/core/src/java/org/apache/solr/handler/sql/SolrSchema.java#L103 So the Sql Schema is not initializing properly for this dataset. I'd be interested in understanding why. If you want to create a

Re: boost parameter produces garbage hits

For your application, I would probably do everything with the qf and pf fields. Your minimally tokenized fields are better evidence for relevance, so weight them higher. Something like this, with phrase matches counting twice as much as word matches: text_minimal^2 text_stem

LTR: Normalize Feature Weights

Hi, Is there a way to normalize the value of fieldValueFeature and OriginalScoreFeature features within some range i.e 0-1. Lets suppose I have 4 products with some field values, I wish to normalize weight within 0 and 1 using func (val-min)/(max-min). Product FieldValue Normalized Value P1 4 1

RE: boost parameter produces garbage hits

Looked at boost a bit more. The # of results remains the same whether the boost parameter is present or not. If it is present the behavior seems to be that if it matches a hit in the result, it does what I expect, however if it does not match the hit, what ends up in the result is completely

Re: Solr LTR model Performance Issues

Hi, I made change in the model by making the LTRScoringModel as immutable and cache hashCode calculation. The response time improved a lot after the change.

Re: solr 7.x sql query returns null

Hi Joel, besides the solr log is there anywhere else i need to go ? anything I need to set to get more detail ? On Thu, 18 Apr 2019 at 10:46, Joel Bernstein wrote: > This let's make sure the jdbc URL is correct. > > Reloading the collection shouldn't effect much unless the schema is >

boost parameter produces garbage hits

Hi, I am trying to understand how the boost (and bq) parameters are supposed to work. My application searches our product schema and returns the best matches. To enable an exactish match on product name we created fields that are minimally tokenized (keyword tokenizer/lowercase). Now I want

Re: Optimizing fq query performance

FYI https://issues.apache.org/jira/browse/SOLR-11437 https://issues.apache.org/jira/browse/SOLR-12488 On Thu, Apr 18, 2019 at 7:24 AM Shawn Heisey wrote: > On 4/17/2019 11:49 PM, John Davis wrote: > > I did a few tests with our instance solr-7.4.0 and field:* vs field:[* TO > > *] doesn't seem

Re: solr 7.x sql query returns null

This query is directly from a web browser to eliminate any downstream components (we use Talend ESB to read / write data into our web application) Any of these queries fail - the URL format is http://localhost:8983/solr/data/sql?stmt=select id from data limit 10

Re: solr 7.x sql query returns null

This let's make sure the jdbc URL is correct. Reloading the collection shouldn't effect much unless the schema is different. But as Shawn mentioned the stack trace is not coming from Solr. Is there more in the logs beyond the Calcite exception? Joel Bernstein http://joelsolr.blogspot.com/ On

Re: solr 7.x sql query returns null

On 4/18/2019 1:47 AM, David Barnett wrote: I have a large solr 7.3 collection 400m + documents. I’m trying to use the Solr JDBC driver to query the data but I get a java.io.IOException: Failed to execute sqlQuery 'select id from document limit 10' against JDBC connection 'jdbc:calcitesolr:'.

Re: bin/post command not working when run from crontab

Jason - thanks for replying and I concur, it makes sense to open a JIRA for this.I'm glad there is an acceptable workaround, at least. I recall doing a fair bit of trial and error, asking 'nix folk and stackoverflow how to handle this stdin situation and honing in on what's there

Re: solr 7.x sql query returns null

Its odd, if I export all docs to JSON, then delete the solr docs and import from my export it works Joel Is there any way to see what it’s complaining about ? On 18 Apr 2019, 09:17 -0500, Joel Bernstein , wrote: > I ask this because SQL/JDBC may return a similar error if you try to run it > on a

Re: solr 7.x sql query returns null

Hi Joel Yes it was always setup as cloud. On Thu, 18 Apr 2019, 15:17 Joel Bernstein, wrote: > Was the original index a Solr Cloud index? > > > > Joel Bernstein > http://joelsolr.blogspot.com/ > > > On Thu, Apr 18, 2019 at 7:48 AM David Barnett > wrote: > > > I have a large solr 7.3 collection

Re: Replica becomes leader when shard was taking a time to update document - Solr 6.1.0

On 4/18/2019 1:00 AM, vishal patel wrote: Thanks for your reply. You are right. I checked GC log and use of GC Viewer I noticed that pause time was 111.4546597 secs. 2019-04-08T13:52:09.939+0100: 796800.430: [GC (Allocation Failure) 796800.431: [ParNew Desired survivor size 2415919104

Re: Solr8.0.0 Time Zone Issue

On 4/18/2019 1:50 AM, Anuj Bhargava wrote: In mySql, date field *date_upload* shows entry as 2019-04-17 However, afer Solr Indexing *date_upload* is being shown as 2019-04-16T18:30:00Z I did change in solr.in.sh, SOLR_TIMEZONE="UTC" to SOLR_TIMEZONE="IST" and did a full-import again. The

Re: Optimizing fq query performance

On 4/17/2019 11:49 PM, John Davis wrote: I did a few tests with our instance solr-7.4.0 and field:* vs field:[* TO *] doesn't seem materially different compared to has_field:1. If no one knows why Lucene optimizes one but not another, it's not clear whether it even optimizes one to be sure.

Re: solr 7.x sql query returns null

I ask this because SQL/JDBC may return a similar error if you try to run it on a non-Solr Cloud index. Joel Bernstein http://joelsolr.blogspot.com/ On Thu, Apr 18, 2019 at 10:16 AM Joel Bernstein wrote: > Was the original index a Solr Cloud index? > > > > Joel Bernstein >

Re: solr 7.x sql query returns null

Was the original index a Solr Cloud index? Joel Bernstein http://joelsolr.blogspot.com/ On Thu, Apr 18, 2019 at 7:48 AM David Barnett wrote: > I have a large solr 7.3 collection 400m + documents. > > I’m trying to use the Solr JDBC driver to query the data but I get a > > >

Re: Solr8.0.0 date search issue

On 4/17/2019 8:45 PM, Anuj Bhargava wrote: I have an issue while searching on the Date field date_upload My Schema file has the following entry for DATE Field ** You haven't shown us the definition for pdate. If it is what the Solr examples have, then it is a DatePointField. My

solr 7.x sql query returns null

I have a large solr 7.3 collection 400m + documents. I’m trying to use the Solr JDBC driver to query the data but I get a java.io.IOException: Failed to execute sqlQuery 'select id from document limit 10' against JDBC connection 'jdbc:calcitesolr:'. Error while executing SQL "select id from

Re: JSON Facet query to retrieve count all collections in Solr 8.0.0

Is there possibility that this could be a bug in the new Solr 8.0.0? Since I do not face the issue in the earlier version, and I have not changed any configuration in this new version. My data in Solr 8.0.0 is freshly re-index directly in Solr 8.0.0, not upgraded from earlier version. Regards,

Solr8.0.0 Time Zone Issue

In mySql, date field *date_upload* shows entry as 2019-04-17 However, afer Solr Indexing *date_upload* is being shown as 2019-04-16T18:30:00Z I did change in solr.in.sh, SOLR_TIMEZONE="UTC" to SOLR_TIMEZONE="IST" and did a full-import again. The entry in *date_upload* is still being shown as

LTR plugin and XGBoost

I would like to use a pairwise ranking model trained with XGBoost in Apache Solr (xgboost objective: rank:pairwise). I guess the XGBoost model should generally be handled by the

Re: Replica becomes leader when shard was taking a time to update document - Solr 6.1.0

Thanks for your reply. You are right. I checked GC log and use of GC Viewer I noticed that pause time was 111.4546597 secs. GC Log : 2019-04-08T13:52:09.198+0100: 796799.689: [CMS-concurrent-mark: 1.676/30.552 secs] [Times: user=93.42 sys=34.11, real=30.55 secs] 2019-04-08T13:52:09.198+0100: