We (all?) agree to do away with "contrib" :-).
I think a folder grouping the modules (that which can plug inside Solr) is
useful as there are a number of them -- as such this is a nice organization
IMO. There's a bunch of other stuff at the top level and I'd rather not
intermix all our modules at
We can have modules, but why do they need to be in an additional folder
deep? Why not just have langid next to solrj and core? Contrib to me
connotes experimental or unsupported, which these things are decidedly not.
On Fri, Jun 11, 2021 at 2:59 PM David Smiley wrote:
> The contrib folder is
The contrib folder is just a folder of modules -- optional plugins for
solr-core. IMO we should simply rename "contrib" to "modules". I think
the only non-module in there is the prometheus exporter which could move
out. Mike, I'm not sure if you have a different notion of what "module"
is? I
I think related to this, I would like to see some "contibs" moved out
from the contrib folder and into proper modules. Right now the
definition of contrib seems to be anything that isn't core or solrj,
but maybe there is room for a backup module that has gcs and s3 and
hdfs all under it. LangId is
It is not depending on timing -- it just includes the timing in its
output (it basically diffs the response message with and without CBs).
Atri
On Fri, Jun 11, 2021 at 8:02 PM Michael Sokolov wrote:
>
> I ran the smoketester (FWIW I always have to pass --tmp-dir /local/tmp
> because my /tmp is
After nuking all settings (i simply removed the whole
lucene.build.properties in my homedir), it still fails. Seems maybe
like less failures though?
I will upload logs to the JIRA issue.
[junit4] Completed [939/939 (4!)] on J2 in 383.02s, 2 tests, 1
failure <<< FAILURES!
[junit4]
*uwesays* if you see test failures with this shebang pattern: don't worry, just
normal!
Uwe
Am June 11, 2021 3:33:46 PM UTC schrieb Michael Sokolov :
>The whole shebang passed on round two for me: SUCCESS!
>[1:00:03.729685]. I guess I'm a +1 to release
>
>On Fri, Jun 11, 2021 at 10:31 AM
The whole shebang passed on round two for me: SUCCESS!
[1:00:03.729685]. I guess I'm a +1 to release
On Fri, Jun 11, 2021 at 10:31 AM Michael Sokolov wrote:
>
> I ran the smoketester (FWIW I always have to pass --tmp-dir /local/tmp
> because my /tmp is not big enough for this thing), but it
I ran the smoketester (FWIW I always have to pass --tmp-dir /local/tmp
because my /tmp is not big enough for this thing), but it failed for
me:
[junit4] Tests with failures [seed: D9C1F978D5A8B019]:
[junit4] - org.apache.solr.util.TestCircuitBreaker.testResponseWithCBTiming
Have to say,
I nuked all my settings and am rerunning with all defaults. I'll
report back what happens/upload log when/if it finishes or fails.
On Fri, Jun 11, 2021 at 9:45 AM Michael Sokolov wrote:
>
> I tried to comment on the JIRA, but it seems to be timing out. Now
> when I go back, SOLR issues are
I tried to comment on the JIRA, but it seems to be timing out. Now
when I go back, SOLR issues are marked as "You can't view this issue
It may have been deleted or you don't have permission to view it."
Waat?
Anyway, Robert you suggested there that maybe the problem is being
surfaced by using a
Thanks very much Robert for detailed investigations, and thanks Jan for
your tests.
I will sort out the problem with my GPG key, but I am not sure what to do
with this SOLR-15473. I've run the smoker test again, and it passed on my
Mac again: SUCCESS! [1:00:03.751500]
Would appreciate more
I believe we can do a fair amount of re-organization pertaining to Jetty
without losing the Jetty configuration that I think is valuable to users
who want to tweak something.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Fri, Jun 11, 2021 at 8:01
Dude, if you can vote +1 when the smoketester passes, then I can vote
-1 when it fails. This is my vote, not your vote. You don't get to
decide about it, or change it in any way.
On Fri, Jun 11, 2021 at 8:04 AM Jan Høydahl wrote:
>
> Does it reproduce for you? Are you suspecting a bug in Solr
Does it reproduce for you? Are you suspecting a bug in Solr that we cannot
ship, or only a bug in the smoketester py itself? The -1 should be about the
released bits, not about other tooling?
My JVM is OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.292-b10, mixed mode)
Jan
> 11. jun. 2021
+1 to a cleanup here for 9.0. As clean and neat organization as possible.
Perhaps rename "dist" -> "lib"?
I wish we could get rid of the server (jetty) folder altogether, and move
everything from server/solr-webapp/webapp/WEB-INF/lib to "lib/deps/". But that
ties into custom boot-class,
Jan, I'm using the same automated smoketester as everyone else. It
fails, so my vote is -1.
On Fri, Jun 11, 2021 at 7:22 AM Jan Høydahl wrote:
>
> Tested on MacOS (Intel), No other verification than smoketester done
>
> SUCCESS! [1:08:19.953492]
>
> +1
>
> Robert - not sure if one test-run
Bumping this conversation up, based on recent communication. I have yet to
take action but really any of us can.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Mon, Nov 23, 2020 at 8:48 AM David Smiley wrote:
> I'll proceed on this with lazy
Tested on MacOS (Intel), No other verification than smoketester done
SUCCESS! [1:08:19.953492]
+1
Robert - not sure if one test-run failure should cancel the build. Our
smoketester and tests are sometimes a bit picky, and does not mean that the
artifacts are faulty.
Jan
> 11. jun. 2021 kl.
Hi Lucene Support Team ,
Objective : Upgrade Lucene 3.6 to 7.6
Description : We have huge data against version Lucene 3.6 .All of this data
needs to upgraded to version Lucene 7.6 without any changes . Requesting your
support on how to proceed with this ?
Regards
Rashmi
I've no idea what happened here - EOF everywhere, insane.
Dawid
On Thu, Jun 10, 2021 at 7:57 PM Apache Jenkins Server
wrote:
>
> Build: https://ci-builds.apache.org/job/Lucene/job/Lucene-Coverage-main/69/
>
> 1724 tests failed.
> FAILED:
>
21 matches
Mail list logo
