That largely depends on how different the 3.4/3.5 java API is from the current version in our trunk (3.0.3). From a maintainability standpoint, it would be easier for us to fix this bug when we've ported Lucene.NET to the same version that java was at when it was fixed. It looks like they added a class and changed another's signature, and then changed all of the comparator classes to inherit from the new one, instead the old. I don't know what that would do to our current version of code, or if that can be worked in without major changes.
Worst case scenario, we can't get it in until we reach 3.4, but I can certainly see what we can do get it in earlier. In the meantime, it seems that Hoss Man has noted a workaround here https://issues.apache.org/jira/browse/LUCENE-3390?focusedCommentId=13088832&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13088832 that can be used. Thanks, Christopher On Wed, Mar 14, 2012 at 6:04 AM, Tom Cabanski <[email protected]> wrote: > I am running into the following problem discussed and fixed in the current > Lucene Java version: > > "While sorting results over a numeric field, documents which do not contain > a value for the sorting field seem to get 0 (ZERO) value in the sort. > (Tested against Double, Float, Int & Long numeric fields ascending and > descending order). > This behavior is unexpected, as zero is "comparable" to the rest of the > values. A better solution would either be allowing the user to define such > a "non-value" default, or always bring those document results as the last > ones." > > Is this something that can get into Lucene.Net soon? See > https://issues.apache.org/jira/browse/LUCENE-3390 for complete information > on the Lucene issue and fix. > > > Tom Cabanski > Software Developer & President <http://southsidesoft.com> > 5702 Kendall Hill Ln > Sugar Land, TX 77479 > 832-766-5961 > > * > * > Profiles: <http://http://www.linkedin.com/in/tomcabanski> > LinkedIn<http://http://www.linkedin.com/in/tomcabanski> > Contact me: [image: Google Talk] [email protected] [image: > Skype]tom.cabanski [image: > MSN] [email protected] > My blog: Top Ten Reasons to Avoid Taking Advanced Distributed System Design > with Udi Dahan< > http://tom.cabanski.com/2012/02/09/top-ten-reasons-to-avoid-taking-advanced-distributed-system-design-with-udi-dahan/ > > > [image: Twitter] <http://twitter.com/tcabanski> Latest tweet: @DataArtist > : Ditto for Azure. It all came back. Funny thing is I think MS never even > bothered to fix Zune problem because it was firmware > Follow @tcabanski <http://twitter.com/tcabanski> Reply > < > http://twitter.com/?status=@tcabanski%20&in_reply_to_status_id=179875723673223170&in_reply_to=tcabanski > > > Retweet > < > http://twitter.com/?status=RT%20%40tcabanski%3A%20%40DataArtist%20%3A%20Ditto%20for%20Azure.%20%20It%20all%20came%20back.%20%20Funny%20thing%20is%20I%20think%20MS%20never%20even%20bothered%20to%20fix%20Zune%20problem%20because%20it%20was%20firmware > > > 05:24 Mar-14<http://twitter.com/tcabanski/statuses/179875723673223168> > Get this email app! > < > http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps > > >
