Re: Performance in Solr 9 / Java 11

2020-08-29 Thread Tomoko Uchida
I believe mr-jar build is enabled in the 8x branch (LUCENE-7966), and the workaround was dropped on the master branch when the minimum java version was bumped up to java 11 (LUCENE-8738); if my understanding is correct. $ jar tf core/lucene-core-8.6.1.jar | grep META-INF/versions

Re: Performance in Solr 9 / Java 11

2020-08-29 Thread Mike Drob
Do you know if these mr-jars are built by default as part of the release process? I definitely had no idea about them when doing 8.5.2 and did not even think to verify anything about it. On Sat, Aug 29, 2020 at 4:05 PM Adrien Grand wrote: > It may only be indirectly related to your question,

Re: Performance in Solr 9 / Java 11

2020-08-29 Thread Adrien Grand
It may only be indirectly related to your question, but there is support for vectorized operations of byte[] arrays that was added in JDK 13 (this blog https://richardstartin.github.io/posts/vectorised-byte-operations explains well what it is about) that we started leveraging for compressing terms

Re: Annoying but harmless exceptions due to filepermissions when running tests

2020-08-29 Thread Erick Erickson
Well, as Uwe and I discussed offline, he’s right and I’m wrong. In CoreContainer [364] there’s code like this: Path userFilesPath = return solrHome.resolve("userfiles"); // TODO make configurable on cfg? try { Files.createDirectories(userFilesPath); // does nothing if already exists } catch

RE: Annoying but harmless exceptions due to filepermissions when running tests

2020-08-29 Thread Uwe Schindler
Hi, this is a bug in the test! It should never ever modify files outside its sandbox. It should not even modify files in build directory. It is fully valid to reject those writes - has nothing to do with users, it's just forbidden by the test framework. Modifying this file is harmful, as it

Annoying but harmless exceptions due to filepermissions when running tests

2020-08-29 Thread Erick Erickson
These exceptions are handled in the code and don’t affect running tests, but they can be a distraction when trying to figure out what’s causing a failure. When CoreContainer is being initialized, these two paths get “Permission Denied” errors since they try to create directories/files.

RE: With ant removed, will GitHub PR job always fail 1st check?

2020-08-29 Thread Uwe Schindler
Thanks, I had no idea where this crazy script is configured. Uwe - Uwe Schindler Achterdiek 19, D-28357 Bremen https://www.thetaphi.de eMail: u...@thetaphi.de From: Tomás Fernández Löbbe Sent: Saturday, August 29, 2020 4:49 AM To: dev@lucene.apache.org Subject: Re: With ant