Both of those look good to include!
Ill keep an eye out for when they get resolved.
- Houston
On Mon, Jul 27, 2020 at 9:16 PM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:
> Can we include SOLR-11611 for 8.6.1? The patch should be simple to test
> out (with someone having a Windows
Can we include SOLR-11611 for 8.6.1? The patch should be simple to test out
(with someone having a Windows machine and VM) and seems like a good one to
fix.
I marked it as a 8.6.1 bug, but please feel free to unmark it (or I can do
so, if you tell me to) if you feel otherwise.
On Tue, Jul 28,
I would say lets update branch_8_6 as well, so that if there's a subsequent
release (say 8.6.2), then someone else isn't tripped over due to this.
On Tue, Jul 28, 2020 at 4:19 AM Gus Heck wrote:
> On master the asciidoctor version is specified in the gradle build, so I
> think only 8x needs an
Came back from holiday and fixed
https://issues.apache.org/jira/browse/SOLR-14671
Can we include it in 8.6.1?
Jan
> 27. jul. 2020 kl. 22:56 skrev Houston Putman :
>
> Added upgrade notes for the autoscaling stuff.
>
> Will begin the release process tomorrow when my GPG Keys will be refreshed
Hi,
We normally don't accept a request of this nature, but let's first see if
Lucene's existing API is adequate for your needs. It seems you are trying
to score documents that don't match the query strictly. Thus it seems that
in some sense, all documents ultimately match your query -- at least
On master the asciidoctor version is specified in the gradle build, so I
think only 8x needs an update.
On Mon, Jul 27, 2020 at 5:29 PM Houston Putman
wrote:
> Nah, 8x and master should be fine. Good find
>
> On Mon, Jul 27, 2020 at 5:11 PM Gus Heck wrote:
>
>> Found it... there's another
Nah, 8x and master should be fine. Good find
On Mon, Jul 27, 2020 at 5:11 PM Gus Heck wrote:
> Found it... there's another critical version not listed in the readme...
> when I did this upgrade it suddenly worked:
>
> asciidoctor (1.5.6.2 < 2.0.10)
>
> Will update README.adoc... won't bother
Found it... there's another critical version not listed in the readme...
when I did this upgrade it suddenly worked:
asciidoctor (1.5.6.2 < 2.0.10)
Will update README.adoc... won't bother with 8_6 branch though unless you
want it.
On Mon, Jul 27, 2020 at 4:57 PM Gus Heck wrote:
> No dice
No dice updated to those versions, ran gem cleanup, still get the error.
Very odd.
build-site:
[java] Relative link points at id that doesn't exist in dest:
the-standard-query-parser.html#differences-between-lucenes-classic-query-parser-and-solrs-standard-query-parser
[java] ...
Added upgrade notes for the autoscaling stuff.
Will begin the release process tomorrow when my GPG Keys will be refreshed
in all of the apache systems.
- Houston
On Mon, Jul 27, 2020 at 4:41 PM Gus Heck wrote:
> Doc changes are in. Still having trouble with that one link in 8x but just
>
I can build on branch_8_6 without issue. And it looks like the offending
line is the same on 8_6 and 8x.
I am using:
ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-darwin16]
jekyll (3.5.0)
jekyll-asciidoc (3.0.0)
slim (4.1.0)
tilt (2.0.10)
concurrent-ruby (1.1.6)
Might be the
Doc changes are in. Still having trouble with that one link in 8x but just
fixed it locally and made sure not to push that change.
On Mon, Jul 27, 2020 at 12:57 PM Gus Heck wrote:
> 8x docs not building smoothly on my laptop... (without changes)
> troubleshooting, checking deps listed in
meh forgot that images get stripped... it shows 3 other places where the
same <<# syntax for an anchor is used...
On Mon, Jul 27, 2020 at 2:42 PM Gus Heck wrote:
> I've verified all the versions for gems mentioned in README.adoc
>
> * HTML version, using Jekyll:
> ** `Ruby` (v2.3 or higher)
>
I've verified all the versions for gems mentioned in README.adoc
* HTML version, using Jekyll:
** `Ruby` (v2.3 or higher)
** The following gems must be installed:
*** `jekyll`: v3.5, not v4.x.
Use `gem install jekyll --force --version 3.5.0` to force install of v3.5.0.
*** `jekyll-asciidoc`: v2.1
8x docs not building smoothly on my laptop... (without changes)
troubleshooting, checking deps listed in README.adoc, etc.
On Mon, Jul 27, 2020 at 11:50 AM Houston Putman
wrote:
> Yeah, push it to branch_8_6. I have to document the upgrade notes for the
> autoscaling stuff anyways.
>
> On Mon,
Yeah, push it to branch_8_6. I have to document the upgrade notes for the
autoscaling stuff anyways.
On Mon, Jul 27, 2020 at 11:27 AM Gus Heck wrote:
> I realized after I went looking for it in the new docs that I didn't
> actually push the doc changes for MOVEREPLICA to 8x (had intended to
I realized after I went looking for it in the new docs that I didn't
actually push the doc changes for MOVEREPLICA to 8x (had intended to verify
that nothing differed in 8x before pushing). Doing that now, and suspect
that we probably want to include it for 8.6.1
On Sat, Jul 25, 2020 at 10:20 PM
Oh that's great. I thought it might be defaulting it in the autoscaling
zookeeper node. Thanks for correcting me!
If that is all that is needed then I'll probably just add something to the
release notes mentioning why the upgrade is necessary.
On Sat, Jul 25, 2020 at 10:21 PM Varun Thacker
Good 'ol software engineering practices is certainly the core of what I
intend, though I am also raising the question of whether or not we want to
consign some defined set of things that plug-in to the far side of those
API's, and whether or not that entails a more explicit notion of what
Short form:
Processing file (History bit 3): HOSS-2020-07-27.csv
Processing file (History bit 2): HOSS-2020-07-20.csv
Processing file (History bit 1): HOSS-2020-07-13.csv
Processing file (History bit 0): HOSS-2020-07-06.csv
Number of AwaitsFix: 33 Number of BadApples: 4
**Annotated tests that
To everyone and especially Gus: I think the "plugin" word in this thread
is basically a stop-word to the intent/scope of the thread. A plugin to
Solr both has been and will be nothing more than a class that's loaded
*dynamically* by a configurable name -- as opposed to a class within Solr
that
Welcome Mike!
On Fri, Jul 24, 2020 at 10:03 PM Anshum Gupta
wrote:
> I am pleased to announce that Mike Drob has accepted the PMC's invitation
> to join.
>
> Congratulations and welcome, Mike!
>
> --
> Anshum Gupta
>
--
Adrien
22 matches
Mail list logo
