[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444739#comment-13444739
]
Uwe Schindler commented on LUCENE-4332:
---
bq. Will this require people to put rhino
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444737#comment-13444737
]
Dawid Weiss commented on LUCENE-4332:
-
bq. Its a number of runner vms used by pitest
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444718#comment-13444718
]
Greg Bowyer commented on LUCENE-4332:
-
{quote}
Greg, what's this responsible for:
{co
[
https://issues.apache.org/jira/browse/SOLR-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444717#comment-13444717
]
Sami Siren commented on SOLR-3768:
--
+1
> add some prelim assertions to Ov
[
https://issues.apache.org/jira/browse/SOLR-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren reopened SOLR-3731:
--
I ran the tests on a slow vm and I do see the failures now, reopening.
> Disallow null Core
Build: https://builds.apache.org/job/Lucene-Solr-Tests-4.x-java7/372/
All tests passed
Build Log:
[...truncated 7546 lines...]
[junit4:junit4] ERROR: JVM J0 ended with an exception, command line:
/usr/local/openjdk7/jre/bin/java -XX:+UseG1GC -Dtests.prefix=tests
-Dtests.seed=7A1F53D49116FA20 -X
[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bowyer updated LUCENE-4332:
Attachment:
LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch
New version
* u
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444635#comment-13444635
]
Greg Bowyer commented on LUCENE-4337:
-
{quote}
I also spend my time in reading JDK so
Gary Yngve created LUCENE-4344:
--
Summary: unit test failing in solr4 beta
Key: LUCENE-4344
URL: https://issues.apache.org/jira/browse/LUCENE-4344
Project: Lucene - Core
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SOLR-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-3768:
---
Attachment: SOLR-3768.patch
Attached patch won't increase the likelihood of the test passing, but it should
m
Hoss Man created SOLR-3768:
--
Summary: add some prelim assertions to OverseerTest
Key: SOLR-3768
URL: https://issues.apache.org/jira/browse/SOLR-3768
Project: Solr
Issue Type: Test
Report
[
https://issues.apache.org/jira/browse/LUCENE-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4343:
Attachment: LUCENE-4343.patch
Here's a first stab.
> Clear up more Tokenizer.setR
Robert Muir created LUCENE-4343:
---
Summary: Clear up more Tokenizer.setReader/TokenStream.reset issues
Key: LUCENE-4343
URL: https://issues.apache.org/jira/browse/LUCENE-4343
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444527#comment-13444527
]
Robert Muir commented on LUCENE-4337:
-
This reminds me of fixing the contrib/remote t
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444500#comment-13444500
]
Uwe Schindler commented on LUCENE-4337:
---
bq. Actually you know what, I think I just
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1397#comment-1397
]
Uwe Schindler commented on LUCENE-4337:
---
The approach is also good - and can also b
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1356#comment-1356
]
Greg Bowyer commented on LUCENE-4337:
-
Actually you know what, I think I just talked
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1345#comment-1345
]
Greg Bowyer edited comment on LUCENE-4337 at 8/30/12 8:47 AM:
-
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bowyer updated LUCENE-4337:
Attachment: ChrootSecurityManagerTest.java
ChrootSecurityManager.java
Gregs altern
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1344#comment-1344
]
Greg Bowyer commented on LUCENE-4337:
-
I have a slightly different approach that I wa
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4337:
--
Attachment: LUCENE-4337.patch
Now also the TestMultiCoreConfBootstrap test was fixed. The prob
[
https://issues.apache.org/jira/browse/SOLR-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-3699:
---
Attachment: SOLR-3699.patch
updated patch to trunk.
Doing this helped uncover another (distinct) case where d
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1310#comment-1310
]
Robert Muir commented on LUCENE-4339:
-
{quote}
I also looked at the code, the handlin
[
https://issues.apache.org/jira/browse/LUCENE-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1303#comment-1303
]
David Smiley commented on LUCENE-4342:
--
Thanks for the bug report. I think there ma
[
https://issues.apache.org/jira/browse/LUCENE-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley reassigned LUCENE-4342:
Assignee: David Smiley
> Issues with prefix tree's Distance Error Percentage
> --
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444397#comment-13444397
]
Uwe Schindler edited comment on LUCENE-4339 at 8/30/12 7:49 AM:
---
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444397#comment-13444397
]
Uwe Schindler commented on LUCENE-4339:
---
I agree with Hoss, the problem is not only
[
https://issues.apache.org/jira/browse/LUCENE-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Itamar Syn-Hershko updated LUCENE-4342:
---
Attachment: unnamed.patch
A failing test
> Issues with prefix tree'
Itamar Syn-Hershko created LUCENE-4342:
--
Summary: Issues with prefix tree's Distance Error Percentage
Key: LUCENE-4342
URL: https://issues.apache.org/jira/browse/LUCENE-4342
Project: Lucene - Cor
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4337:
--
Attachment: LUCENE-4337.patch
Attached is a patch that works around some problems:
- the JMX
[
https://issues.apache.org/jira/browse/LUCENE-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444380#comment-13444380
]
Raimund Merkert commented on LUCENE-4341:
-
This is one of the (automatically gene
[
https://issues.apache.org/jira/browse/SOLR-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444377#comment-13444377
]
Yonik Seeley commented on SOLR-3731:
Operator error... after trying to get timings and
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444366#comment-13444366
]
Hoss Man edited comment on LUCENE-4339 at 8/30/12 7:01 AM:
---
bq.
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444366#comment-13444366
]
Hoss Man commented on LUCENE-4339:
--
bq. Whoah: its not really a time bomb. The time bomb
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444358#comment-13444358
]
Uwe Schindler commented on LUCENE-4339:
---
Can we please stop bringing the backwards
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444355#comment-13444355
]
Robert Muir commented on LUCENE-4339:
-
{quote}
I don't think that users complaining o
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444351#comment-13444351
]
Robert Muir commented on LUCENE-4339:
-
{quote}
Bottom line: If we have a simple patch
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444350#comment-13444350
]
Shai Erera commented on LUCENE-4339:
I don't think that users complaining or not shou
[
https://issues.apache.org/jira/browse/SOLR-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444346#comment-13444346
]
Sami Siren commented on SOLR-3731:
--
bq. I did 10 full "ant test" runs on my box (on trunk
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444344#comment-13444344
]
Hoss Man commented on LUCENE-4339:
--
bq. And I had not realized our official back-compat
[
https://issues.apache.org/jira/browse/SOLR-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444342#comment-13444342
]
Yonik Seeley commented on SOLR-3731:
I did 10 full "ant test" runs on my box (on trunk
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444328#comment-13444328
]
Michael McCandless commented on LUCENE-4339:
+1 to separate what we do for 4.
Thanks Alan! I just committed that...
Mike McCandless
http://blog.mikemccandless.com
On Wed, Aug 29, 2012 at 1:57 PM, Alan Woodward
wrote:
> Obviously overlooked when adapting from ChecksumIndexOutput. Patch inline,
> it didn't seem worth opening a JIRA for!
>
> Alan Woodward
> www.romseysof
Hi all,
It looks like we have very special "command" character here… which mirrors
some "visible" images… but it is still invalid XML when I try to validate in
Eclipse…
Solr-4.0.0-BETA
0
237
true
1
index
10
enrich_keywords_string_mv
0
0
0
0
0
0
Obviously overlooked when adapting from ChecksumIndexOutput. Patch inline, it
didn't seem worth opening a JIRA for!
Alan Woodward
www.romseysoftware.co.uk
diff --git
a/lucene/core/src/java/org/apache/lucene/store/ChecksumIndexInput.java
b/lucene/core/src/java/org/apache/lucene/store/ChecksumI
[
https://issues.apache.org/jira/browse/SOLR-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444215#comment-13444215
]
Steven Rowe edited comment on SOLR-2747 at 8/30/12 4:13 AM:
bq.
[
https://issues.apache.org/jira/browse/SOLR-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444215#comment-13444215
]
Steven Rowe commented on SOLR-2747:
---
bq. the patch i sent to the ML:
Cool, thanks, I was
[
https://issues.apache.org/jira/browse/SOLR-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444196#comment-13444196
]
Sami Siren commented on SOLR-3731:
--
bq. i raised the loop to go even longer and still some
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444179#comment-13444179
]
Robert Muir commented on LUCENE-4339:
-
I can commit this to 4.x once Mike has had a c
[
https://issues.apache.org/jira/browse/LUCENE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444177#comment-13444177
]
Uwe Schindler commented on LUCENE-4336:
---
Too bad! But thanks for reporting back!
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444175#comment-13444175
]
Robert Muir commented on LUCENE-4337:
-
Patch is really simple and nice.
Maybe we sh
[
https://issues.apache.org/jira/browse/SOLR-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated SOLR-2747:
--
Attachment: SOLR-2747_fix.patch
the patch i sent to the ML:
But we should decide where we want the outp
[
https://issues.apache.org/jira/browse/LUCENE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444172#comment-13444172
]
Robert Muir commented on LUCENE-4336:
-
Thanks for working on this. I tested today and
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444170#comment-13444170
]
Uwe Schindler commented on LUCENE-4337:
---
And a 3rd thing:
- SecurityPermission was
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4339:
--
Comment: was deleted
(was: And a 3rd thing:
- SecurityPermission was not granted, but TIKA vio
another random side note: whereever we 'output' this changes in the
solr source distribution, I think we should somehow also run
changes2html on the lucene CHANGES.txt too?
This way solr users looking at the solr src dist can easily see 'all
the changes' ?
On Wed, Aug 29, 2012 at 12:25 PM, Robert
Sorry, correct patch: the script is in lucene/site/changes. the target
dir ... this seems to make sense? or should we put it somewhere else?
prepare-release succeeds with this:
Index: solr/build.xml
===
--- solr/build.xml (revis
On Wed, Aug 29, 2012 at 12:10 PM, Steven Rowe (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/SOLR-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Steven Rowe reopened SOLR-2747:
> ---
>
>
> Solr-Artifacts-trunk failed b
[
https://issues.apache.org/jira/browse/SOLR-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe reopened SOLR-2747:
---
Solr-Artifacts-trunk failed because {{changes2html.pl}} couldn't be found: from
[https://builds.apache.or
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444143#comment-13444143
]
Robert Muir commented on LUCENE-4339:
-
{quote}
I would like to applay the current pat
[
https://issues.apache.org/jira/browse/SOLR-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444140#comment-13444140
]
Mark Miller commented on SOLR-3731:
---
P.S. only after this was committed did I start seein
[
https://issues.apache.org/jira/browse/SOLR-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444139#comment-13444139
]
Mark Miller commented on SOLR-3731:
---
I keep seeing this sometimes too - i raised the loop
> This has always been part of our index back-compat promise. Ie, as
> long as all segments were written with version N-1, in version N of
> Lucene you can open up the index and do anything (searching,
> adding/updating/deleting docs, etc.) with it.
+1 - I think a lot of people that would try the
The current (4.0-BETA) CHANGES.txt does say the following:
"Mixed flex/pre-flex indexes are perfectly fine -- the two
emulation layers (flex API on pre-flex index, and pre-flex API on
flex index) will remap the access as required. So on upgrading to
4.0 you can start indexing new docume
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444100#comment-13444100
]
Uwe Schindler commented on LUCENE-4339:
---
And a 3rd thing:
- SecurityPermission was
[
https://issues.apache.org/jira/browse/LUCENE-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444093#comment-13444093
]
Robert Muir commented on LUCENE-4341:
-
Do you have any more information (maybe from y
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4337:
--
Attachment: LUCENE-4337.patch
Very simple patch:
This adds some sysprops to the test runner t
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444088#comment-13444088
]
Robert Muir commented on LUCENE-4339:
-
{quote}
The whole backwards compatibility disc
[
https://issues.apache.org/jira/browse/SOLR-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444087#comment-13444087
]
Martijn van Groningen commented on SOLR-3762:
-
I made a small mistake in the la
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444085#comment-13444085
]
Uwe Schindler commented on LUCENE-4339:
---
Finally, please apply this patch +
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444084#comment-13444084
]
Uwe Schindler commented on LUCENE-4339:
---
bq. I don't think the patch should be comm
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444083#comment-13444083
]
Uwe Schindler commented on LUCENE-4339:
---
The whole backwards compatibility discusss
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444082#comment-13444082
]
Yonik Seeley commented on LUCENE-4339:
--
Folks: I still see no objections to enabling
[
https://issues.apache.org/jira/browse/SOLR-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444061#comment-13444061
]
Yonik Seeley commented on SOLR-3765:
Thanks for tracking this down Per, I agree this is
[
https://issues.apache.org/jira/browse/SOLR-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444047#comment-13444047
]
Jesse MacVicar commented on SOLR-3762:
--
Hmm, slightly different error this time?
SEVE
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444011#comment-13444011
]
Robert Muir commented on LUCENE-4339:
-
I'm trying to stop this issue from being 'chan
[
https://issues.apache.org/jira/browse/LUCENE-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444007#comment-13444007
]
Robert Muir commented on LUCENE-4340:
-
Sounds like a good plan. We can use ivy config
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444005#comment-13444005
]
Yonik Seeley commented on LUCENE-4339:
--
You're trying to leverage your vote on this
Raimund Merkert created LUCENE-4341:
---
Summary: java.lang.ArrayIndexOutOfBoundsException in
BooleanScorer2.score
Key: LUCENE-4341
URL: https://issues.apache.org/jira/browse/LUCENE-4341
Project: Luce
Glenn MacStravic created SOLR-3767:
--
Summary: Multiple Simultaenous DIH running show status in same
window
Key: SOLR-3767
URL: https://issues.apache.org/jira/browse/SOLR-3767
Project: Solr
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443997#comment-13443997
]
Robert Muir commented on LUCENE-4339:
-
It makes total sense. I gave my technical rati
[
https://issues.apache.org/jira/browse/LUCENE-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443996#comment-13443996
]
Adrien Grand commented on LUCENE-4226:
--
bq. Do you want to open a separate issue for
[
https://issues.apache.org/jira/browse/LUCENE-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443995#comment-13443995
]
Adrien Grand commented on LUCENE-4340:
--
Maybe the easiest way to go would be to have
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443990#comment-13443990
]
Yonik Seeley commented on LUCENE-4339:
--
{quote}
All you have to do is back down from
Adrien Grand created LUCENE-4340:
Summary: Move all codecs but Lucene40 to a module
Key: LUCENE-4340
URL: https://issues.apache.org/jira/browse/LUCENE-4340
Project: Lucene - Core
Issue Type:
On Wed, Aug 29, 2012 at 6:48 AM, Michael McCandless
wrote:
> I think it makes sense to allow deletions against 3.x segments?
>
> This has always been part of our index back-compat promise. Ie, as
> long as all segments were written with version N-1, in version N of
> Lucene you can open up the in
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443979#comment-13443979
]
Robert Muir commented on LUCENE-4339:
-
I already told you I agree with 'a' in this pa
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443972#comment-13443972
]
Uwe Schindler commented on LUCENE-4339:
---
I have 2 things:
a) Allow it for Lucene 4
[
https://issues.apache.org/jira/browse/LUCENE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443967#comment-13443967
]
Robert Muir commented on LUCENE-4339:
-
All you have to do is back down from the gener
[
https://issues.apache.org/jira/browse/LUCENE-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443962#comment-13443962
]
Robert Muir commented on LUCENE-4226:
-
{quote}
I was also thinking that some codecs s
On Wed, Aug 29, 2012 at 5:13 AM, Uwe Schindler wrote:
> Hi Robert,
>
> In my opinion, we *must* allow changing LiveDocs in any codec that is for
> migration (also in 5.x) but forced read-only. Of course in 5.x no longer
> needs support for 3.x indexes, but that’s another story. The reason for th
[
https://issues.apache.org/jira/browse/SOLR-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson reassigned SOLR-2701:
Assignee: (was: Erick Erickson)
I won't be getting to this any time soon
I think it makes sense to allow deletions against 3.x segments?
This has always been part of our index back-compat promise. Ie, as
long as all segments were written with version N-1, in version N of
Lucene you can open up the index and do anything (searching,
adding/updating/deleting docs, etc.)
Thanks Mike.
D.
On Wed, Aug 29, 2012 at 12:25 PM, Michael McCandless
wrote:
> I fixed (rev 1378493).
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Wed, Aug 29, 2012 at 2:56 AM, Dawid Weiss
> wrote:
>> Reproduces for me with:
>>
>>> [junit4:junit4] 2> NOTE: reproduce with: ant
[
https://issues.apache.org/jira/browse/LUCENE-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-4335:
---
Attachment: LUCENE-4335.patch
Small patch to have createLevAutomata.py do the hg che
I fixed (rev 1378493).
Mike McCandless
http://blog.mikemccandless.com
On Wed, Aug 29, 2012 at 2:56 AM, Dawid Weiss
wrote:
> Reproduces for me with:
>
>> [junit4:junit4] 2> NOTE: reproduce with: ant test
>> -Dtestcase=GroupFacetCollectorTest
>> -Dtests.method=testMVGroupedFacetingWithDelet
[
https://issues.apache.org/jira/browse/LUCENE-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443939#comment-13443939
]
Adrien Grand commented on LUCENE-4226:
--
Thanks Dawid and Eks for your feedback!
bq.
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443927#comment-13443927
]
Uwe Schindler edited comment on LUCENE-4337 at 8/29/12 8:19 PM:
---
[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443927#comment-13443927
]
Uwe Schindler commented on LUCENE-4337:
---
I checked already: We dont really need a S
Hi Robert,
In my opinion, we *must* allow changing LiveDocs in any codec that is for
migration (also in 5.x) but forced read-only. Of course in 5.x no longer needs
support for 3.x indexes, but that’s another story. The reason for this
*requirement* (and therefore the issue is blocker) is the sp
1 - 100 of 111 matches
Mail list logo
