[
https://issues.apache.org/jira/browse/SOLR-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884985#comment-16884985
]
ASF subversion and git services commented on SOLR-13472:
Commit
[
https://issues.apache.org/jira/browse/SOLR-13619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya updated SOLR-13619:
Attachment: SOLR-13619.patch
Status: Open (was: Open)
Here's a patch
[
https://issues.apache.org/jira/browse/SOLR-13619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882548#comment-16882548
]
Ishan Chattopadhyaya edited comment on SOLR-13619 at 7/15/19 9:36 AM:
Alan Woodward created LUCENE-8918:
-
Summary: Catch null terms in PhraseQuery early
Key: LUCENE-8918
URL: https://issues.apache.org/jira/browse/LUCENE-8918
Project: Lucene - Core
Issue Type:
romseygeek opened a new pull request #785: LUCENE-8918: Disallow null terms in
PhraseQuery
URL: https://github.com/apache/lucene-solr/pull/785
It is currently possible to create a PhraseQuery consisting of a single
`null` term,
which will then cause NullPointerExceptions deep inside
[
https://issues.apache.org/jira/browse/LUCENE-8883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885095#comment-16885095
]
Christine Poerschke commented on LUCENE-8883:
-
Both the script changes and the results of
[
https://issues.apache.org/jira/browse/LUCENE-8811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884930#comment-16884930
]
Atri Sharma commented on LUCENE-8811:
-
[~jpountz] I had originally raised a patch which implemented
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-Windows/368/
Java: 64bit/jdk-11.0.3 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC
11 tests failed.
FAILED:
org.apache.solr.cloud.LegacyCloudClusterPropTest.testCreateCollectionSwitchLegacyCloud
Error Message:
IOException occurred when
[
https://issues.apache.org/jira/browse/LUCENE-8811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884944#comment-16884944
]
Adrien Grand commented on LUCENE-8811:
--
Thanks! I'll revert this change from 8.x and 8.2 in the
Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-8.2/4/
No tests ran.
Build Log:
[...truncated 24963 lines...]
[asciidoctor:convert] asciidoctor: ERROR: about-this-guide.adoc: line 1:
invalid part, must have at least one section (e.g., chapter, appendix, etc.)
[asciidoctor:convert]
[
https://issues.apache.org/jira/browse/LUCENE-8811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884939#comment-16884939
]
Atri Sharma commented on LUCENE-8811:
-
[~jpountz] Yeah, that is what I was thinking of, but I see
Adrien Grand created LUCENE-8917:
Summary: Remove the "Direct" doc-value format
Key: LUCENE-8917
URL: https://issues.apache.org/jira/browse/LUCENE-8917
Project: Lucene - Core
Issue Type:
[
https://issues.apache.org/jira/browse/SOLR-13240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884951#comment-16884951
]
Richard Goodman edited comment on SOLR-13240 at 7/15/19 8:52 AM:
-
Morning
[
https://issues.apache.org/jira/browse/SOLR-13240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Goodman updated SOLR-13240:
---
Attachment: SOLR-13240.patch
> UTILIZENODE action results in an exception
>
[
https://issues.apache.org/jira/browse/SOLR-13240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884951#comment-16884951
]
Richard Goodman commented on SOLR-13240:
Morning [~cpoerschke], So I wasn't sure as to why I was
Alan Woodward created LUCENE-8916:
-
Summary: GraphTokenStreamFiniteStrings.FiniteStringsTokenStream
does not play well with subsequent TokenFilters
Key: LUCENE-8916
URL:
[
https://issues.apache.org/jira/browse/SOLR-13619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885015#comment-16885015
]
ASF subversion and git services commented on SOLR-13619:
Commit
[
https://issues.apache.org/jira/browse/SOLR-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885014#comment-16885014
]
ASF subversion and git services commented on SOLR-13472:
Commit
atris opened a new pull request #784: LUCENE-8810: Honor MaxClausesCount in
BooleanQuery During Flattening
URL: https://github.com/apache/lucene-solr/pull/784
BooleanQuery will always try to flatten nested clauses during
rewrite. However, this can cause the maximum number of clauses
Hmm that's possible, although the jump is bigger than anything I
observed while testing. I assume these charts are building off of
apache/master, or something close to that? If so, then the timing is
off a bit. LUCENE-8781 was pushed quite a while before that, and then
Atri Sharma created LUCENE-8919:
---
Summary: Query Metadata Aggregator
Key: LUCENE-8919
URL: https://issues.apache.org/jira/browse/LUCENE-8919
Project: Lucene - Core
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/LUCENE-8915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Atri Sharma updated LUCENE-8915:
Description: RateLimiter does not allow dynamic configuration of the rate
limit today. This
romseygeek commented on issue #772: Payload-stored position length intervals
URL: https://github.com/apache/lucene-solr/pull/772#issuecomment-511303962
Re-ordering raises an interesting problem, which is that we immediately hit
LUCENE-7398 again - shared-prefix synonyms start breaking,
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/24401/
Java: 64bit/jdk-12.0.1 -XX:+UseCompressedOops -XX:+UseG1GC
1 tests failed.
FAILED: org.apache.solr.cloud.NestedShardedAtomicUpdateTest.test
Error Message:
Error from server at http://127.0.0.1:43697/collection1: no servers
Build: https://builds.apache.org/job/Lucene-Solr-BadApples-Tests-master/415/
1 tests failed.
FAILED: org.apache.solr.schema.TestCloudSchemaless.test
Error Message:
Error from server at http://127.0.0.1:42969/fky/collection1: Error trying to
proxy request for url:
[
https://issues.apache.org/jira/browse/LUCENE-8916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885109#comment-16885109
]
Alan Woodward commented on LUCENE-8916:
---
Interestingly, the patch attached to LUCENE-8644 will fix
iverase opened a new pull request #783: LUCENE-8914: Move compare logic to
IntersectVisitor in FloatPointNearestNeighbor
URL: https://github.com/apache/lucene-solr/pull/783
This change proposes to move the logic for discarding inner modes to the
IntersectVisitor.
Atri Sharma created LUCENE-8915:
---
Summary: Allow RateLimiter To Have Dynamic Limits
Key: LUCENE-8915
URL: https://issues.apache.org/jira/browse/LUCENE-8915
Project: Lucene - Core
Issue Type:
FYI I added a note to
https://issues.apache.org/jira/browse/LUCENE-8811, I think it's too
breaking for 8.2 and should wait for 9.0. We can mitigate LUCENE-8810
in 8.x by disabling the flattening of inner disjunctions when this
would create too many clauses in a single BooleanQuery. I'll work with
[
https://issues.apache.org/jira/browse/LUCENE-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885010#comment-16885010
]
Uwe Schindler commented on LUCENE-8911:
---
Hi [~tomoko],
sorry for the delay (was in "weekend
[
https://issues.apache.org/jira/browse/LUCENE-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885044#comment-16885044
]
Alan Woodward commented on LUCENE-8917:
---
+1 - I spent some time trying to convert this to
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/5259/
Java: 64bit/jdk-11.0.3 -XX:+UseCompressedOops -XX:+UseSerialGC
1 tests failed.
FAILED: org.apache.solr.core.TestDynamicLoadingUrl.testDynamicLoadingUrl
Error Message:
{ "responseHeader":{ "status":400, "QTime":3},
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-8.2/3/
2 tests failed.
FAILED: org.apache.lucene.document.TestXYMultiPolygonShapeQueries.testRandomBig
Error Message:
Java heap space
Stack Trace:
java.lang.OutOfMemoryError: Java heap space
at
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.2-Windows/146/
Java: 64bit/jdk1.8.0_201 -XX:-UseCompressedOops -XX:+UseParallelGC
3 tests failed.
FAILED:
org.apache.solr.client.solrj.io.stream.StreamDecoratorTest.testClassifyStream
Error Message:
expected:<0.0> but
Ignacio Vera created LUCENE-8914:
Summary: Small improvement in FloatPointNearestNeighbor
Key: LUCENE-8914
URL: https://issues.apache.org/jira/browse/LUCENE-8914
Project: Lucene - Core
Issue
Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-master/1391/
No tests ran.
Build Log:
[...truncated 24576 lines...]
[asciidoctor:convert] asciidoctor: ERROR: about-this-guide.adoc: line 1:
invalid part, must have at least one section (e.g., chapter, appendix, etc.)
[
https://issues.apache.org/jira/browse/LUCENE-8811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884904#comment-16884904
]
Adrien Grand commented on LUCENE-8811:
--
I was reviewing the changelog for 8.2, this change looks a
[
https://issues.apache.org/jira/browse/LUCENE-8811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884932#comment-16884932
]
Adrien Grand commented on LUCENE-8811:
--
[~atris] If the patch you are thinking of is the one on
Raised a PR: https://github.com/apache/lucene-solr/pull/784
On Mon, Jul 15, 2019 at 2:10 PM Adrien Grand wrote:
>
> FYI I added a note to
> https://issues.apache.org/jira/browse/LUCENE-8811, I think it's too
> breaking for 8.2 and should wait for 9.0. We can mitigate LUCENE-8810
> in 8.x by
The change to Lucene 8.2.0 snapshot was done on July 10th. Previous to that
the Lucene version was 8.1.0.
On Mon, Jul 15, 2019 at 12:53 PM Michael Sokolov wrote:
> Hmm that's possible, although the jump is bigger than anything I
> observed while testing. I assume these charts are building off
Hi,
We observed using a snapshot of Lucene 8.2 that there is an increase of
around 30% on the memory usage of IndexReaders for some of the test
datasets, for example:
https://elasticsearch-benchmarks.elastic.co/#tracks/http-logs/nightly/default/30d
We suspect this is due to this change:
[
https://issues.apache.org/jira/browse/SOLR-13619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885012#comment-16885012
]
ASF subversion and git services commented on SOLR-13619:
Commit
atris commented on issue #784: LUCENE-8810: Honor MaxClausesCount in
BooleanQuery During Flattening
URL: https://github.com/apache/lucene-solr/pull/784#issuecomment-511348137
cc @jpountz
ant test for both Lucene and Solr pass, however, the existing Max Clause
Limits test
[
https://issues.apache.org/jira/browse/SOLR-13240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885125#comment-16885125
]
Christine Poerschke commented on SOLR-13240:
Thanks [~Goodman] for persevering despite
[
https://issues.apache.org/jira/browse/SOLR-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885185#comment-16885185
]
ASF subversion and git services commented on SOLR-13472:
Commit
[
https://issues.apache.org/jira/browse/SOLR-13619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya updated SOLR-13619:
Fix Version/s: 8.2
> Kerberos: 403 when node doesn't host collection
>
[
https://issues.apache.org/jira/browse/SOLR-13619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885186#comment-16885186
]
ASF subversion and git services commented on SOLR-13619:
Commit
[
https://issues.apache.org/jira/browse/SOLR-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-13621:
--
Description:
Streaming Expressions and Math Expressions are now mature on the query side.
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-MacOSX/243/
Java: 64bit/jdk-12.0.1 -XX:+UseCompressedOops -XX:+UseParallelGC
1 tests failed.
FAILED:
org.apache.solr.client.solrj.io.stream.MathExpressionTest.testGammaDistribution
Error Message:
0.7954005541640882 0.8194307823181612
Thanks for the nice test, Adrien. Yes, the tradeoff of direct
addressing is heavily data-dependent. I think we can improve the
situation here by tracking, per-FST instance, the size increase we're
seeing while building (or perhaps do a preliminary pass before
building) in order to decide whether
[
https://issues.apache.org/jira/browse/SOLR-13375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885317#comment-16885317
]
ASF subversion and git services commented on SOLR-13375:
Commit
jpountz commented on issue #784: LUCENE-8810: Honor MaxClausesCount in
BooleanQuery During Flattening
URL: https://github.com/apache/lucene-solr/pull/784#issuecomment-511378685
> Can you merge master back into your branch so that it sees the revert of
LUCENE-8811 as well?
Actually
[
https://issues.apache.org/jira/browse/SOLR-13622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885162#comment-16885162
]
Joel Bernstein edited comment on SOLR-13622 at 7/15/19 12:42 PM:
-
The
I dug this a bit and suspect that the issue is mostly with one field
that is not part of the data but auto-generated: the ID field. It is a
slight variant of Flake IDs, so it's not random, it includes a
timestamp and a sequence number, and I suspect that its patterns
combined with the larger
Those are rally tracks so I expect you can download them:
https://github.com/elastic/rally-tracks
On Mon, Jul 15, 2019 at 2:33 PM Michael Sokolov wrote:
> OK, both LUCENE-8781 and LUCENE-8895 were introduced in 8.2.0. I see
> most of the other data sets report an increase more in the 10-15%
>
atris commented on issue #784: LUCENE-8810: Honor MaxClausesCount in
BooleanQuery During Flattening
URL: https://github.com/apache/lucene-solr/pull/784#issuecomment-511400026
@jpountz Thanks for your comments. I have opened #787 which fixes your
comments and is against 8x
atris closed pull request #784: LUCENE-8810: Honor MaxClausesCount in
BooleanQuery During Flattening
URL: https://github.com/apache/lucene-solr/pull/784
This is an automated message from the Apache Git Service.
To respond
atris opened a new pull request #787: LUCENE-8810: Honor MaxClausesCount in
BooleanQuery
URL: https://github.com/apache/lucene-solr/pull/787
During Flattening, BooleanQuery will always try to flatten
nested clauses during rewrite. However, this can cause the
maximum number of clauses
[
https://issues.apache.org/jira/browse/LUCENE-8811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885120#comment-16885120
]
ASF subversion and git services commented on LUCENE-8811:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-8811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885121#comment-16885121
]
ASF subversion and git services commented on LUCENE-8811:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-13622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885162#comment-16885162
]
Joel Bernstein commented on SOLR-13622:
---
The StreamContext has a reference to the SolrCore where
romseygeek opened a new pull request #786: LUCENE-8916:
GraphTokenStreamFiniteStrings preserves all incoming attributes
URL: https://github.com/apache/lucene-solr/pull/786
Instead of cloning terms and position increments, we keep track of all
incoming
attributes and replay them from
[
https://issues.apache.org/jira/browse/SOLR-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-13621:
--
Description:
Streaming Expressions and Math Expressions are now mature on the query side.
[
https://issues.apache.org/jira/browse/LUCENE-8811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885154#comment-16885154
]
ASF subversion and git services commented on LUCENE-8811:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-13635:
--
Component/s: streaming expressions
> Add SolrLogStream Streaming Expression
>
Joel Bernstein created SOLR-13635:
-
Summary: Add SolrLogStream Streaming Expression
Key: SOLR-13635
URL: https://issues.apache.org/jira/browse/SOLR-13635
Project: Solr
Issue Type:
[
https://issues.apache.org/jira/browse/SOLR-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-13635:
--
Description: The SolrLogStream will parse Solr Log Format and create tuples
with fields that
[
https://issues.apache.org/jira/browse/SOLR-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-13635:
--
Environment: (was: The SolrLogStream will parse Solr Log Format and
create tuples with
[
https://issues.apache.org/jira/browse/SOLR-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya resolved SOLR-13480.
-
Resolution: Fixed
> Collection creation failure when using Kerberos
[
https://issues.apache.org/jira/browse/SOLR-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885212#comment-16885212
]
Ishan Chattopadhyaya commented on SOLR-13480:
-
Hi [~moshebla], after I committed SOLR-13472
[
https://issues.apache.org/jira/browse/SOLR-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877454#comment-16877454
]
Ishan Chattopadhyaya edited comment on SOLR-13472 at 7/15/19 1:14 PM:
[
https://issues.apache.org/jira/browse/LUCENE-8810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-8810.
--
Resolution: Fixed
Fix Version/s: (was: 8.1.1)
8.2
> Flattening
jpountz commented on a change in pull request #784: LUCENE-8810: Honor
MaxClausesCount in BooleanQuery During Flattening
URL: https://github.com/apache/lucene-solr/pull/784#discussion_r303404207
##
File path: lucene/core/src/test/org/apache/lucene/search/TestBooleanQuery.java
jpountz commented on a change in pull request #784: LUCENE-8810: Honor
MaxClausesCount in BooleanQuery During Flattening
URL: https://github.com/apache/lucene-solr/pull/784#discussion_r303404451
##
File path: lucene/core/src/test/org/apache/lucene/search/TestBooleanQuery.java
[
https://issues.apache.org/jira/browse/SOLR-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-13621:
--
Description:
Streaming Expressions and Math Expressions are now mature on the query side.
[
https://issues.apache.org/jira/browse/SOLR-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-13621:
--
Description:
Streaming Expressions and Math Expressions are now mature on the query side.
[
https://issues.apache.org/jira/browse/LUCENE-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885204#comment-16885204
]
Tomoko Uchida commented on LUCENE-8911:
---
Thanks [~thetaphi],
{quote}Just to confirm: The generated
thomaswoeckinger commented on issue #755: SOLR-13592: Introduce
EmbeddedSolrTestBase for better integration tests
URL: https://github.com/apache/lucene-solr/pull/755#issuecomment-511391348
Still nothing?
This is an automated
thomaswoeckinger commented on issue #665: Fixes SOLR-13539
URL: https://github.com/apache/lucene-solr/pull/665#issuecomment-511391449
Still nothing?
This is an automated message from the Apache Git Service.
To respond to the
[
https://issues.apache.org/jira/browse/SOLR-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-13621:
--
Description:
Streaming Expressions and Math Expressions are now mature on the query side.
[
https://issues.apache.org/jira/browse/SOLR-13632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-13632:
--
Component/s: streaming expressions
> Allow the integrate Stream Evaluator to compute integrals
atris commented on issue #787: LUCENE-8810: Honor MaxClausesCount in
BooleanQuery
URL: https://github.com/apache/lucene-solr/pull/787#issuecomment-511405603
Thanks for merging @jpountz !
This is an automated message from the
[
https://issues.apache.org/jira/browse/SOLR-13375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885252#comment-16885252
]
ASF subversion and git services commented on SOLR-13375:
Commit
[
https://issues.apache.org/jira/browse/SOLR-13619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya resolved SOLR-13619.
-
Resolution: Fixed
> Kerberos: 403 when node doesn't host collection
>
[
https://issues.apache.org/jira/browse/SOLR-13636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-13636:
--
Summary: Add CommonEventFormatStream (CEF) Streaming Expression (was: Add
[
https://issues.apache.org/jira/browse/SOLR-13636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-13636:
--
Summary: Add CommonEventFormatStream (CEF) Streaming Expressions (was: Add
Joel Bernstein created SOLR-13636:
-
Summary: Add CommenEventFormatStream (CEF) Streaming Expressions
Key: SOLR-13636
URL: https://issues.apache.org/jira/browse/SOLR-13636
Project: Solr
Issue
[
https://issues.apache.org/jira/browse/LUCENE-8810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885235#comment-16885235
]
ASF subversion and git services commented on LUCENE-8810:
-
Commit
jpountz merged pull request #787: LUCENE-8810: Honor MaxClausesCount in
BooleanQuery
URL: https://github.com/apache/lucene-solr/pull/787
This is an automated message from the Apache Git Service.
To respond to the message,
OK, both LUCENE-8781 and LUCENE-8895 were introduced in 8.2.0. I see
most of the other data sets report an increase more in the 10-15%
range, which is expected. I'm curious what the makeup of that http
logs data set is -- I guess it's HTTP logs :) Is the data public?
On Mon, Jul 15, 2019 at 7:23
[
https://issues.apache.org/jira/browse/SOLR-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885194#comment-16885194
]
Jason Gerlowski commented on SOLR-13472:
bq. Attaching a patch. As per this, the authorization
[
https://issues.apache.org/jira/browse/SOLR-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya resolved SOLR-13472.
-
Resolution: Fixed
Fix Version/s: 8.2
Thanks [~adfel70].
> HTTP requests
[
https://issues.apache.org/jira/browse/SOLR-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885232#comment-16885232
]
Ishan Chattopadhyaya commented on SOLR-13472:
-
You're right when you mentioned,
bq. the
[
https://issues.apache.org/jira/browse/LUCENE-8810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885240#comment-16885240
]
ASF subversion and git services commented on LUCENE-8810:
-
Commit
atris commented on issue #779: LUCENE-8762: Introduce Specialized Impacts For
Doc + Freq
URL: https://github.com/apache/lucene-solr/pull/779#issuecomment-511408229
Any thoughts on this one? I am hoping this will bring gains to our nightly
benchmarks :)
+1 to rollback and having a 8.3 as soon as we nail this down (even if that
is days or 1-2 weeks after 8.2).
On Mon, 15 Jul, 2019, 9:22 PM Michael Sokolov, wrote:
> I guess whether we roll back depends on timing. I think we are close
> to a release though, and these changes are complex and will
My guess is that the code is designed this way to avoid boilerplate
more than for performance reasons. Mike McCandless might have more
information?
+1 to disable array-with-gaps but keep the logic for now
On Mon, Jul 15, 2019 at 5:52 PM Michael Sokolov wrote:
>
> I guess whether we roll back
Mike Sokolov created LUCENE-8920:
Summary: Reduce size of FSTs due to use of direct-addressing
encoding
Key: LUCENE-8920
URL: https://issues.apache.org/jira/browse/LUCENE-8920
Project: Lucene - Core
I guess whether we roll back depends on timing. I think we are close
to a release though, and these changes are complex and will require
further testing, so rollback seems reasonable to me. I think from code
management perspective it will be simplest to disable direct
addressing for now, rather
magibney commented on issue #772: Payload-stored position length intervals
URL: https://github.com/apache/lucene-solr/pull/772#issuecomment-511527663
Agreed, @romseygeek; just to clarify, re-ordering may _raise_ the problem,
but doesn't _introduce_ it. This is indeed a variant of the issue
1 - 100 of 143 matches
Mail list logo
