SUCCESS! [0:56:11.512628]

+1.

D.

On Mon, Sep 11, 2017 at 10:31 AM, Jan Høydahl <[email protected]> wrote:
> Thanks Christine
>
> The WARN msgs are not blockers.
> However, I tested the DIH ‘db’  example with 6.6.0 and it works, indexing 16
> documents.
> Also re-tested the example directly in branch_7_0 and it fails there too, so
> this seems to be a regression, but I don’t know what the bug is.
>
> Created https://issues.apache.org/jira/browse/SOLR-11348 as a blocker for
> this, leaving it up to RM to lower the severity if the vote passes.
>
> -0
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
> 11. sep. 2017 kl. 04.53 skrev Christine Poerschke (BLOOMBERG/ LONDON)
> <[email protected]>:
>
> Thanks Jan for these observations!
>
> The Couldn't add files WARNing seems be pre-existing and I've created
> SOLR-11346 to explore if actually it should be an ERROR/exception.
>
> About the solr.LatLonType WARNing, does the DIH example actually use those
> field types? If not could they simply be removed instead of replaced, unless
> perhaps we wish to keep all the example configs similar as much as possible
> even if that means that some examples will have unused stuff?
>
> Those are my observations i.e. also not a vote.
>
> Christine
>
> From: [email protected] At: 09/10/17 22:19:11
> To: [email protected]
> Subject: Re: [VOTE] Release Apache Lucene/Solr 7.0.0 RC3
>
> DIH example that failed in RC2 now loads, but still with three WARN level
> logs which is not ideal from a fresh install...
>
> WARN  - 2017-09-10 20:44:02.927; [   x:mail]
> org.apache.solr.core.SolrConfig; Couldn't add files from
> /Users/janhoy/Downloads/solr-7.0.0/contrib/dataimporthandler/lib filtered by
> .*\.jar to classpath:
> /Users/janhoy/Downloads/solr-7.0.0/contrib/dataimporthandler/lib
> WARN  - 2017-09-10 20:44:03.454; [   x:db]
> org.apache.solr.core.SolrResourceLoader; Solr loaded a deprecated
> plugin/analysis class [solr.LatLonType]. Please consult documentation how to
> replace it accordingly.
> WARN  - 2017-09-10 20:44:03.454; [   x:mail]
> org.apache.solr.core.SolrResourceLoader; Solr loaded a deprecated
> plugin/analysis class [solr.LatLonType]. Please consult documentation how to
> replace it accordingly.
>
>
> However, DIH “db” example does not work ootb. But it could have been broken
> in earlier versions too?
>
> ERROR - 2017-09-10 20:46:29.317; [   x:db]
> org.apache.solr.common.SolrException; Exception while processing: item
> document : SolrInputDocument(fields:
> []):org.apache.solr.handler.dataimport.DataImportHandlerException: Unable to
> execute query: select * from item Processing Document # 1
> at
> org.apache.solr.handler.dataimport.DataImportHandlerException.wrapAndThrow(DataImportHandlerException.java:69)
>         …
> Caused by: java.sql.SQLException: error in script file line: 2
> /Users/janhoy/Downloads/solr-7.0.0/example/example-DIH/hsqldb/ex system
> object cannot be modified in statement [CREATE CACHED TABLE ITEM(ID
> CHAR(8),NAME VARCHAR(100),MANU VARCHAR(50),WEIGHT REAL,PRICE REAL,POPULARITY
> INTEGER,INCLUDES VARCHAR(200),LAST_MODIFIED TIMESTAMP DEFAULT NOW)]
> at org.hsqldb.jdbc.JDBCUtil.sqlException(Unknown Source)
>
>
> The “files” example that failed in RC2 now works.
>
> This is not a vote, just an observation :) Will run smoke tester later.
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
> 9. sep. 2017 kl. 07.10 skrev Anshum Gupta <[email protected]>:
>
> Please vote for the third release candidate for Apache Lucene/Solr 7.0.0.
>
> Artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-7.0.0-RC3-rev3ba304b29825a94249c5145b3f5061e87b87d8f8/
>
> You can run the smoke tester directly from this command:
>
>   python3 -u dev-tools/scripts/smokeTestRelease.py
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-7.0.0-RC3-rev3ba304b29825a94249c5145b3f5061e87b87d8f8/
>
> Reminder: You would need to run this from branch_7_0.
>
> Here's my +1:
>
> SUCCESS! [0:35:25.819530]
>
> -Anshum
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to