One of the benefits of moving forward with the conversion of the Java
Lucene, is that they're using more recent versions of Java that support
things like generics and enums, so the direct port is getting more and more
like .NET, though not in all respects of course. I'm of the mind, though,
that
I'm not that proficient in JIRA yet, and can only find 22 open issues
outstanding. Is this correct, or am I missing something?
-r
On Fri, Dec 23, 2011 at 2:38 PM, Prescott Nasser geobmx...@hotmail.comwrote:
You can look at the jira issues for Java lucene 3.0.3 and submit patches
for 2.9.4g
but I guess the future of 2.9.4g depends on the extent that it is becoming
more .NET like
My intention while I was creating that branch was just to make 2.9.4 a
little bit more .Net like(+ maybe some performance).
I used many codes from 3.0.3 Java. So it is somewhere between 2.9.4 3.0.3
But I
That's 40 issues that the Java Lucene team tagged as needed for 3.0.3 release
(so they are all closed atm) I will try to port many/most of these over this
week into our JIRA so we can track them for ourselves.
From: geobmx...@hotmail.com To:
Any reason we can't continue this g branch and make it more and more .net like?
I was thinking about what we've expressed at goals - we want a line by line
port - it's easy to maintain parity with java and easy to compare. We also want
a more .NET version - the g branch gets this started -
[
https://issues.apache.org/jira/browse/SOLR-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176548#comment-13176548
]
Uwe Schindler commented on SOLR-2346:
-
Nice fix, is in-line with the other charset
[
https://issues.apache.org/jira/browse/SOLR-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176654#comment-13176654
]
Erick Erickson commented on SOLR-2438:
--
Hmmm, it's clear that reading this patch is
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x-java7/1377/
2 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.update.processor.SignatureUpdateProcessorFactoryTest
Error Message:
Cannot delete
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/1369/
1 tests failed.
REGRESSION: org.apache.solr.search.TestRealTimeGet.testStressGetRealtime
Error Message:
java.lang.AssertionError: Some threads threw uncaught exceptions!
Stack Trace:
java.lang.RuntimeException:
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x/11949/
No tests ran.
Build Log (for compile errors):
[...truncated 3058 lines...]
[javac] public Collection getFileNames() throws IOException {
[javac] ^
[javac]
[
https://issues.apache.org/jira/browse/SOLR-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved SOLR-2982.
---
Resolution: Fixed
Upgrade Apache Commons Codec to version 1.6 in order to add new Beider-Morse
edismax does not respect pf params using non-tokenized fields
-
Key: SOLR-2988
URL: https://issues.apache.org/jira/browse/SOLR-2988
Project: Solr
Issue Type: Bug
Affects
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x/11951/
2 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.update.processor.SignatureUpdateProcessorFactoryTest
Error Message:
Cannot delete
As far as I can see, this started intermittently failing at the start
of Dec (and only on 3x).
Anyone have an idea of what changed to cause this?
-Yonik
http://www.lucidimagination.com
On Wed, Dec 28, 2011 at 3:06 PM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
Build:
[
https://issues.apache.org/jira/browse/SOLR-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176796#comment-13176796
]
Erick Erickson commented on SOLR-1931:
--
In the trunk (4.x) version, (from Muir) below.
I will check later, maybe the usual out of disk space problem.
--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.thetaphi.de
Yonik Seeley yo...@lucidimagination.com schrieb:
As far as I can see, this started intermittently failing at the start
of Dec (and only on 3x).
Anyone have
Solr admin (Luke request handler) doesn't order the fields alphabetically
-
Key: SOLR-2989
URL: https://issues.apache.org/jira/browse/SOLR-2989
Project: Solr
Issue
[
https://issues.apache.org/jira/browse/SOLR-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-2989:
-
Attachment: SOLR-2989.patch
First cut at a patch. This is for 3x because that's where I happened
[
https://issues.apache.org/jira/browse/SOLR-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson reassigned SOLR-2989:
Assignee: Erick Erickson
Solr admin (Luke request handler) doesn't order the fields
Sorry, misunderstood the mail. Jenkins is fine, it’s a test problem occurring
sometimes. Last run was fine.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de/ http://www.thetaphi.de
eMail: u...@thetaphi.de
From: Uwe Schindler [mailto:u...@thetaphi.de]
[
https://issues.apache.org/jira/browse/SOLR-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-2947:
---
Attachment: SOLR-2947.patch
Ok. here is the patch, which fixes issue with destroy() and
Erick,
I want to fix good old DIH multi-threading issue. It doesn't work at all.
I've decided to start after SOLR-2382 is committed.
Firstly I've found two minor issues introduced by SOLR-2382:
- SOLR-2933 - It has patch polished by James D;
- SOLR-2947 - I attached fix for the minor subject
Howdy, I am new to the Lucene project. I started looking at
LUCENE-2987https://issues.apache.org/jira/browse/LUCENE-2987.
It appears the QueryParser accepts a Conjunction OR and AND, but not the
lowercase version. Is this something that needs to be changed with the
grammar to accept these as
Mikhail:
Fair warning. I know nothing, zero, zilch about DIH so as far as code
reviews etc, I can do some
superficial stuff, but a deep understanding of DIH is not something I
can provide.
What I can do is help nudge it along, test, do the gruntwork that goes
with actually checking
something in.
[
https://issues.apache.org/jira/browse/SOLR-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176961#comment-13176961
]
Otis Gospodnetic commented on SOLR-1931:
Is that actually true? What if one is
[
https://issues.apache.org/jira/browse/SOLR-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-2802:
---
Attachment: SOLR-2802_update_processor_toolkit.patch
Lance: see my 01/Oct/11 comment responding to Erik's
[
https://issues.apache.org/jira/browse/LUCENE-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176998#comment-13176998
]
Steven Rowe commented on LUCENE-3655:
-
bq. I don't know of any survey's about what's
[
https://issues.apache.org/jira/browse/LUCENE-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-3655:
Attachment: LUCENE-3655.patch
Modified the patch to use the xml.etree.ElementTree module, which
Oh, I see now, we need to import the issues as well as the changesets. I
guess I can just start to work on the Lucene 3.0.3 issues on trunk until
they are imported?
-r
On Wed, Dec 28, 2011 at 5:22 PM, Prescott Nasser geobmx...@hotmail.comwrote:
That's 40 issues that the Java Lucene team
Yeah that would work
Sent from my Windows Phone
From: Rory Plaire
Sent: 12/28/2011 10:05 PM
To: lucene-net-...@lucene.apache.org
Subject: Re: [Lucene.Net] Merge 3.0.3 into trunk and other forward progress
Oh, I see now, we need to import the issues as well as the
30 matches
Mail list logo
