[
https://issues.apache.org/jira/browse/SOLR-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178016#comment-14178016
]
ASF subversion and git services commented on SOLR-6530:
---
Commit 16332
[
https://issues.apache.org/jira/browse/SOLR-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178013#comment-14178013
]
ASF subversion and git services commented on SOLR-6530:
---
Commit 16332
[
https://issues.apache.org/jira/browse/SOLR-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178012#comment-14178012
]
ASF subversion and git services commented on SOLR-6530:
---
Commit 16332
[
https://issues.apache.org/jira/browse/SOLR-6573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177980#comment-14177980
]
Jan Høydahl commented on SOLR-6573:
---
Good comment from [~hossman_luc...@fucit.org] about
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/4281/
Java: 32bit/jdk1.7.0_67 -server -XX:+UseG1GC
1 tests failed.
REGRESSION: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.testDistribSearch
Error Message:
expected:<0> but was:<1>
Stack Trace:
java.lang.AssertionError: expected:
Hey Jan,
if the goal here is to get the un-parsed query string, independent of any
possible localparams, then the "best" way to do that is to use the
QParser.getParser statc method to parse things, and then pull the "v"
param (QueryParsing.V) out of the Local Params that you get.
Even that mu
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/662/
3 tests failed.
REGRESSION: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.testDistribSearch
Error Message:
The Monkey ran for over 20 seconds and no jetties were stopped - this is worth
investigating!
Stack Trace:
java.
[
https://issues.apache.org/jira/browse/SOLR-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177565#comment-14177565
]
Shawn Heisey commented on SOLR-6058:
Here's an "out of left field" comment: I was look
[
https://issues.apache.org/jira/browse/SOLR-6351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177564#comment-14177564
]
Hoss Man commented on SOLR-6351:
bq. The reason for previous random test failures were fac
[
https://issues.apache.org/jira/browse/SOLR-6573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177547#comment-14177547
]
ASF subversion and git services commented on SOLR-6573:
---
Commit 16332
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/11333/
Java: 64bit/jdk1.8.0_20 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
REGRESSION: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.testDistribSearch
Error Message:
shard2 is not consistent. Got 62 from
http://12
[
https://issues.apache.org/jira/browse/SOLR-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl reassigned SOLR-6636:
-
Assignee: Jan Høydahl
> Documentation refers to wrong factory classes for some suggesters
> --
[
https://issues.apache.org/jira/browse/SOLR-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl resolved SOLR-6636.
---
Resolution: Fixed
Thanks for reporting. Fixed in
https://cwiki.apache.org/confluence/display/solr/Sugg
[
https://issues.apache.org/jira/browse/SOLR-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177480#comment-14177480
]
Jan Høydahl commented on SOLR-6630:
---
+1 to rename!
> Deprecate the "implicit" router and
[
https://issues.apache.org/jira/browse/SOLR-6573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177447#comment-14177447
]
ASF subversion and git services commented on SOLR-6573:
---
Commit 16332
[
https://issues.apache.org/jira/browse/LUCENE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177446#comment-14177446
]
Robert Muir commented on LUCENE-6013:
-
+1
We may want to followup with some modifica
[
https://issues.apache.org/jira/browse/LUCENE-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177439#comment-14177439
]
Robert Muir commented on LUCENE-6015:
-
+1
> Revisit DocIdSetBuilder's heuristic to s
[
https://issues.apache.org/jira/browse/LUCENE-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-6015:
-
Attachment: LUCENE-6015.patch
Here is a patch proposal that updates the shift value from 14 to 10
[
https://issues.apache.org/jira/browse/LUCENE-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177424#comment-14177424
]
Adrien Grand commented on LUCENE-6015:
--
Hmm, correct... This explains why performanc
[
https://issues.apache.org/jira/browse/LUCENE-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177420#comment-14177420
]
Robert Muir commented on LUCENE-6015:
-
FWIW the changes in fuzzy should all be noise
[
https://issues.apache.org/jira/browse/LUCENE-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177418#comment-14177418
]
Adrien Grand commented on LUCENE-6015:
--
Here are the results of luceneutil benchmark
TEST_JVM_ARGS=-XX:+UseG1GC
On Mon, Oct 20, 2014 at 4:00 PM, wrote:
> Build: builds.flonkings.com/job/Lucene-5x-Linux-Java7-64-test-only/33783/
>
> All tests passed
>
> Build Log:
> [...truncated 715 lines...]
>[junit4] JVM J3: stdout was not empty, see:
> /var/lib/jenkins/workspace/Lucene-5
Adrien Grand created LUCENE-6015:
Summary: Revisit DocIdSetBuilder's heuristic to switch to
FixedBitSet
Key: LUCENE-6015
URL: https://issues.apache.org/jira/browse/LUCENE-6015
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177412#comment-14177412
]
Adrien Grand commented on LUCENE-5293:
--
Although the elias-fano set is smaller in th
Build: builds.flonkings.com/job/Lucene-5x-Linux-Java7-64-test-only/33783/
All tests passed
Build Log:
[...truncated 715 lines...]
[junit4] JVM J3: stdout was not empty, see:
/var/lib/jenkins/workspace/Lucene-5x-Linux-Java7-64-test-only/checkout/lucene/build/core/test/temp/junit4-J3-20141020_2
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11491/
Java: 32bit/jdk1.7.0_67 -server -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeyNothingIsSafeTest.testDistribSearch
Error Message:
There were too many update fails - we expect it can happen, but
[
https://issues.apache.org/jira/browse/LUCENE-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177382#comment-14177382
]
ASF subversion and git services commented on LUCENE-5969:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177378#comment-14177378
]
ASF subversion and git services commented on LUCENE-5969:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177376#comment-14177376
]
ASF subversion and git services commented on LUCENE-5969:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177373#comment-14177373
]
Tomás Fernández Löbbe commented on SOLR-6349:
-
I'll iterate this patch to impro
[
https://issues.apache.org/jira/browse/LUCENE-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177279#comment-14177279
]
Robert Muir commented on LUCENE-6014:
-
Well again my concern is, the optimization is
[
https://issues.apache.org/jira/browse/LUCENE-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177264#comment-14177264
]
Michael McCandless commented on LUCENE-6014:
+1 to just nuke this scary optim
[
https://issues.apache.org/jira/browse/LUCENE-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177251#comment-14177251
]
ASF subversion and git services commented on LUCENE-5969:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-6013:
---
Attachment: LUCENE-6013.patch
Good idea Rob: I added the static asserts, for IndexOpt
[
https://issues.apache.org/jira/browse/LUCENE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177189#comment-14177189
]
Robert Muir commented on LUCENE-6013:
-
Looks much simpler!
I guess the one thing is
[
https://issues.apache.org/jira/browse/SOLR-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177177#comment-14177177
]
Grant Ingersoll commented on SOLR-6058:
---
I've started a branch for this:
https://svn
[
https://issues.apache.org/jira/browse/SOLR-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177176#comment-14177176
]
ASF subversion and git services commented on SOLR-6058:
---
Commit 16331
[
https://issues.apache.org/jira/browse/LUCENE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-6013:
---
Attachment: LUCENE-6013.patch
New patch, fixing docs and factoring out separate metho
[
https://issues.apache.org/jira/browse/LUCENE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177154#comment-14177154
]
Michael McCandless commented on LUCENE-6013:
I'll update the javadocs for the
[
https://issues.apache.org/jira/browse/LUCENE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-6013:
---
Attachment: LUCENE-6013.patch
New patch, just pulling out the index options as their
: I committed a fix.
Thanks Adrien
(FYI: it it wasn't obvious for folks, this was a glitch in a new test i
added for LUCENE-5961)
:
: On Sun, Oct 19, 2014 at 10:11 AM, Apache Jenkins Server
: wrote:
: > Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/652/
: >
: > 1 tests fa
Varun Thacker created SOLR-6637:
---
Summary: Solr should have a way to restore a core
Key: SOLR-6637
URL: https://issues.apache.org/jira/browse/SOLR-6637
Project: Solr
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SOLR-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-6633:
-
Attachment: SOLR-6633.patch
added support in the default example schema
> let /update/json/docs store the
[
https://issues.apache.org/jira/browse/SOLR-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177079#comment-14177079
]
Varun Thacker commented on SOLR-6151:
-
It's late here so I can look into the test tomor
Hi,
How do I verify if Solr core reload is successful or not? I use Solr 4.6.
To reload the core I send the below request:
http://hostname:7090/solr/admin/cores?action=RELOAD&core=core0&wt=json
Also is the above request synchronous ( I mean will the reload happen
before the response is recieve
[
https://issues.apache.org/jira/browse/SOLR-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177068#comment-14177068
]
Tomás Fernández Löbbe commented on SOLR-6151:
-
Yes, I saw it's a timeout, but a
[
https://issues.apache.org/jira/browse/SOLR-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177055#comment-14177055
]
Varun Thacker commented on SOLR-6151:
-
Hi Tomas,
It's a timeout issue again unfortunat
Balazs Endresz created SOLR-6636:
Summary: Documentation refers to wrong factory classes for some
suggesters
Key: SOLR-6636
URL: https://issues.apache.org/jira/browse/SOLR-6636
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177016#comment-14177016
]
Tomás Fernández Löbbe commented on SOLR-6151:
-
There was a new failure of this
[
https://issues.apache.org/jira/browse/LUCENE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176926#comment-14176926
]
Robert Muir commented on LUCENE-6013:
-
No, its good to fix the style, its just scary
[
https://issues.apache.org/jira/browse/LUCENE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176921#comment-14176921
]
Michael McCandless commented on LUCENE-6013:
Thanks Rob, sorry about the nois
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/653/
1 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.testDistribSearch
Error Message:
expected:<0> but was:<2>
Stack Trace:
java.lang.AssertionError: expected:<0> but was:<2>
at
__randomizedtestin
[
https://issues.apache.org/jira/browse/LUCENE-5424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand closed LUCENE-5424.
Resolution: Fixed
> FilteredQuery useRandomAccess() should use cost()
> ---
Thomas Blitz created SOLR-6635:
--
Summary: Cursormark should support skipping/goto functionality
Key: SOLR-6635
URL: https://issues.apache.org/jira/browse/SOLR-6635
Project: Solr
Issue Type: Impr
[
https://issues.apache.org/jira/browse/LUCENE-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176853#comment-14176853
]
Robert Muir commented on LUCENE-6014:
-
As far as i can see, the assumption seems to b
[
https://issues.apache.org/jira/browse/LUCENE-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176822#comment-14176822
]
Daniel Aschauer commented on LUCENE-6012:
-
Thanks, Michael!
Yes, i recognized tha
Robert Muir created LUCENE-6014:
---
Summary: Lucene41PostingsWriter.advance() doc scanning is buggy
Key: LUCENE-6014
URL: https://issues.apache.org/jira/browse/LUCENE-6014
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-6014:
Summary: Lucene41PostingsReader.advance() doc scanning is buggy (was:
Lucene41PostingsWriter.advan
[
https://issues.apache.org/jira/browse/LUCENE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176811#comment-14176811
]
Robert Muir commented on LUCENE-6013:
-
Patch looks good.
I'm afraid about FieldInfos
[
https://issues.apache.org/jira/browse/LUCENE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-6013:
---
Attachment: LUCENE-6013.patch
Patch, I think it's ready.
I think this one is easier
[
https://issues.apache.org/jira/browse/LUCENE-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176793#comment-14176793
]
Michael McCandless commented on LUCENE-6012:
This is just a [sensible] limita
[
https://issues.apache.org/jira/browse/LUCENE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176790#comment-14176790
]
Robert Muir commented on LUCENE-1252:
-
I was fairly specific about how to tackle the
[
https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176785#comment-14176785
]
adrianhsm commented on SOLR-5473:
-
I tried to compile on origin/branch_5x, and then start s
[
https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
adrianhsm updated SOLR-5473:
Comment: was deleted
(was: I tried to compile on origin/branch_5x, and then start solr 5.0 with 2
nodes.crea
Build: https://builds.apache.org/job/Lucene-Solr-Maven-5.x/736/
No tests ran.
Build Log:
[...truncated 24597 lines...]
BUILD FAILED
/usr/home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-5.x/build.xml:540:
The following error occurred while executing this line:
/usr/home/jenkins/jenkins-sla
Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java7/4928/
1 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeySafeLeaderTest.testDistribSearch
Error Message:
expected:<0> but was:<1>
Stack Trace:
java.lang.AssertionError: expected:<0> but was:<1>
at
__randomizedtest
Michael McCandless created LUCENE-6013:
--
Summary: Remove IndexableFieldType.indexed()
Key: LUCENE-6013
URL: https://issues.apache.org/jira/browse/LUCENE-6013
Project: Lucene - Core
Issue
Daniel Aschauer created LUCENE-6012:
---
Summary: AnalyzingSuggester exception because of length
restriction: java.lang.IllegalArgumentException: len must be <= 32767; got 38751
Key: LUCENE-6012
URL: https://issues
Build: builds.flonkings.com/job/Lucene-trunk-Linux-Java7-64-test-only/97421/
1 tests failed.
REGRESSION: org.apache.lucene.util.TestSparseFixedBitSet.testRamBytesUsed
Error Message:
expected:<728> but was:<6968>
Stack Trace:
java.lang.AssertionError: expected:<728> but was:<6968>
at
__
My bad, my latest commit had more changes than expected. I'll fix.
On Mon, Oct 20, 2014 at 10:16 AM, wrote:
> *BUILD FAILURE*
> Build URL
> https://build-eu-1.elasticsearch.org/job/lucene_trunk_linux_java7_64_test_only/7953/
> Project:lucene_trunk_linux_java7_64_test_only Date of build:Mon, 20
I committed a fix.
On Sun, Oct 19, 2014 at 10:11 AM, Apache Jenkins Server
wrote:
> Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/652/
>
> 1 tests failed.
> REGRESSION: org.apache.lucene.queries.function.TestValueSources.testQuery
>
> Error Message:
> The top-reader used to c
[
https://issues.apache.org/jira/browse/LUCENE-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176701#comment-14176701
]
ASF subversion and git services commented on LUCENE-5961:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-6633:
-
Labels: EaseOfUse (was: )
> let /update/json/docs store the source json as well
>
[
https://issues.apache.org/jira/browse/SOLR-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-6633:
-
Description:
it is a common requirement to store the entire JSON as a field in Solr.
we can have a extra
[
https://issues.apache.org/jira/browse/LUCENE-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176695#comment-14176695
]
ASF subversion and git services commented on LUCENE-5961:
-
Commit
Varun Thacker created SOLR-6634:
---
Summary: The Collections API should have a UNLOAD and LOAD command
Key: SOLR-6634
URL: https://issues.apache.org/jira/browse/SOLR-6634
Project: Solr
Issue Type
[
https://issues.apache.org/jira/browse/SOLR-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-6633:
-
Attachment: SOLR-6633.patch
> let /update/json/docs store the source json as well
> ---
[
https://issues.apache.org/jira/browse/LUCENE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176689#comment-14176689
]
Michael McCandless commented on LUCENE-1252:
+1 to this plan.
Except if poss
[
https://issues.apache.org/jira/browse/SOLR-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-6633:
-
Description:
it is a common requirement to store the entire JSON as a field in Solr.
we can have a extra
Noble Paul created SOLR-6633:
Summary: let /update/json/docs store the source json as well
Key: SOLR-6633
URL: https://issues.apache.org/jira/browse/SOLR-6633
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SOLR-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul reassigned SOLR-6633:
Assignee: Noble Paul
> let /update/json/docs store the source json as well
> ---
81 matches
Mail list logo
