Michael Busch wrote:
There are currently 9 issues in Jira targeted for 2.2:
Good progress! Already down to 3 within a day!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Doron Cohen wrote:
This is new API, so I was kinda waiting for some feedback on it.
Another passible issue is that it expands FieldCache and
FieldcacheImpl - while LUCENE-831 "Complete overhaul of
FieldCache API/Implementation" is also changing it.
So I think this can wait for the next release.
[
https://issues.apache.org/jira/browse/LUCENE-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-848:
-
Fix Version/s: (was: 2.2)
Alright. Clearing the fix version to not block 2.2.
> Add support
[
https://issues.apache.org/jira/browse/LUCENE-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500903
]
Steven Parkes commented on LUCENE-848:
--
I'll leave the hosting site to others; I don't know enough about apache
[
https://issues.apache.org/jira/browse/LUCENE-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500902
]
Hoss Man commented on LUCENE-848:
-
is there any reason not to host these on lucene.apache.org instead of the zone?
I
[
https://issues.apache.org/jira/browse/LUCENE-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500901
]
Michael Busch commented on LUCENE-848:
--
OK I see, that makes sense. I think we can clear the fix version here?
[
https://issues.apache.org/jira/browse/LUCENE-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500896
]
Steven Parkes commented on LUCENE-848:
--
Grant was looking at hosting a copy of the dataset on zones so that we'd
[
https://issues.apache.org/jira/browse/LUCENE-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500895
]
Michael Busch commented on LUCENE-894:
--
Has anybody objections against the approach in the latest
patch? If not,
[
https://issues.apache.org/jira/browse/LUCENE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-876:
-
Fix Version/s: (was: 2.2)
Clearing the fix version as this shouldn't block a 2.2 release.
S
[
https://issues.apache.org/jira/browse/LUCENE-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500893
]
Michael Busch commented on LUCENE-848:
--
I'm not familiar with this patch but looking at the recent comments it l
> > Whatever files also need to be included along with the jars in order to
> > make the maven distribution complete that can't be built completley
> > dynamicly (ie: the md5 files) can certainly be commited into the
> > repository ... but if making a release requires a lot of manual
upating to
>
> And this isn't just for our users. There are a lot of significant
> changes being proposed (or already committed) to the merging/indexing
> process, and I know I, for one, would benefit from having a good,
> coherent, unbroken writeup of it in the javadocs after the issues
> have been worked o
[
https://issues.apache.org/jira/browse/LUCENE-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500863
]
Daniel Naber commented on LUCENE-763:
-
Thanks, Steven. Your javadoc changes have also been committed now.
> Luc
On Jun 1, 2007, at 2:54 PM, Michael Busch wrote:
On the other hand I'm not sure why we would need a code freeze. I
think
it will take longer than just one or two weeks to improve the docs
significantly. We should probably open some Jira issues for the
different spots where we want to add doc
Chris Hostetter wrote:
: yet incorporate voting. In the past, we've not always voted on release
: artifacts, but that's Apache policy. A release should not be made
: unless its binary file has at least 3 +1 votes from PMC members. I
Is that really a hard and fast policy? My reading of the vo
[
https://issues.apache.org/jira/browse/LUCENE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500814
]
Yonik Seeley commented on LUCENE-901:
-
> huh? queryNorm is passed down by BooleanWeight to all of the sub clauses
: yet incorporate voting. In the past, we've not always voted on release
: artifacts, but that's Apache policy. A release should not be made
: unless its binary file has at least 3 +1 votes from PMC members. I
Is that really a hard and fast policy? My reading of the voting policy
docs is that
Grant Ingersoll wrote:
What say people about my suggestion of implementing a "code freeze"
for 1-2 weeks prior to a release wherein we work on documentation and
cleaning up JIRA? Perhaps we _strive_ to have every committer (and
others are welcome) to try to javadoc a set of files or to clean
[
https://issues.apache.org/jira/browse/LUCENE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500811
]
Daniel Naber commented on LUCENE-759:
-
Can this issue be closed or is there anything still open?
> Add n-gram t
[
https://issues.apache.org/jira/browse/LUCENE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen resolved LUCENE-875.
Resolution: Fixed
Fixed - we remain with not failing a build due to javadoc warnings or errors -
v
Grant Ingersoll wrote:
What say people about my suggestion of implementing a "code freeze" for
1-2 weeks prior to a release
The process we're using on Hadoop is to have a feature freeze at a
specified date. Trunk is branched at that point. Only blocker issues
are permitted to be applied to
Michael Busch wrote on 01/06/2007 09:31:02:
> - LUCENE-446: "search.function - (1) score based on
> field value, (2) simple score customizability", Doron Cohen
> This looks ready to commit, Doron?
This is new API, so I was kinda waiting for some feedback on it.
Another passible issue is that
[
https://issues.apache.org/jira/browse/LUCENE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch reassigned LUCENE-887:
Assignee: Michael Busch
> Interruptible segment merges
>
>
>
[
https://issues.apache.org/jira/browse/LUCENE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500802
]
Michael Busch commented on LUCENE-887:
--
> I think we should keep it out of core (ie, as subclasses as you've don
[
https://issues.apache.org/jira/browse/LUCENE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500794
]
Michael Busch commented on LUCENE-887:
--
> I think you are right: just removing the call to flushAfterInterrupt()
[
https://issues.apache.org/jira/browse/LUCENE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500782
]
Hoss Man commented on LUCENE-901:
-
> From a scoring perspective, it's a multiplier that's only used at the top
> lev
[
https://issues.apache.org/jira/browse/LUCENE-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen resolved LUCENE-900.
Resolution: Fixed
Lucene Fields: [Patch Available] (was: [New])
Fixed.
> Enable Java asser
[
https://issues.apache.org/jira/browse/LUCENE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500780
]
Michael McCandless commented on LUCENE-887:
---
> > Say there are 2 addDocument calls in-flight, and the first
[
https://issues.apache.org/jira/browse/LUCENE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500779
]
Doug Cutting commented on LUCENE-901:
-
Float.MAX_VALUE seems like a better choice then 1 [ ... ]
With nested que
[
https://issues.apache.org/jira/browse/LUCENE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500766
]
Michael Busch commented on LUCENE-887:
--
> Actually the leftover files from the aborted merge *should* be deleted
On Jun 1, 2007, at 12:31 PM, Michael Busch wrote:
Hi Team,
since we released Lucene 2.1 in February there have been powerful
new features
like "point-in-time searching" (LUCENE-710),
"Payloads" (LUCENE-755) and
"API for pre-analyzed fields" (LUCENE-580), good performance
improvements lik
[
https://issues.apache.org/jira/browse/LUCENE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned LUCENE-510:
--
Assignee: (was: Grant Ingersoll)
I don't have time at the moment
> IndexOutput.wri
[
https://issues.apache.org/jira/browse/LUCENE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-510:
---
Fix Version/s: (was: 2.2)
> IndexOutput.writeString() should write length in bytes
>
[
https://issues.apache.org/jira/browse/LUCENE-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-900:
---
Attachment: lucene-900.patch
As discussed above this enables java assertions in tests.
All tests pass
[
https://issues.apache.org/jira/browse/LUCENE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-887:
-
Fix Version/s: (was: 2.2)
> Interruptible segment merges
>
>
>
[
https://issues.apache.org/jira/browse/LUCENE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500756
]
Michael Busch commented on LUCENE-901:
--
> Float.MAX_VALUE seems like a better choice then 1, but I haven't reall
[
https://issues.apache.org/jira/browse/LUCENE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-854:
--
Fix Version/s: (was: 2.2)
> Create merge policy that doesn't periodically inadverte
"Michael Busch" <[EMAIL PROTECTED]> wrote:
> - LUCENE-854: "Create merge policy that doesn't periodically inadvertently
> optimize", Michael McCandless
> Do you want to get this into 2.2, Mike?
No, I don't think this should block a 2.2 release. I will clear the
Fix version on it
Hi Team,
since we released Lucene 2.1 in February there have been powerful new
features
like "point-in-time searching" (LUCENE-710), "Payloads" (LUCENE-755) and
"API for pre-analyzed fields" (LUCENE-580), good performance
improvements like
"multi-level skipping" (LUCENE-866), "improved buffe
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-794:
---
Attachment: spanhighlighter7.patch
Minor update to straighten a few things out.
- Replaced custom Ca
[
https://issues.apache.org/jira/browse/LUCENE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500725
]
Yonik Seeley commented on LUCENE-902:
-
A few points:
- positionIncrements can also be >1 (the patch explicitly ch
[
https://issues.apache.org/jira/browse/LUCENE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500722
]
Yonik Seeley commented on LUCENE-901:
-
>From a scoring perspective, it's a multiplier that's only used at the top
[
https://issues.apache.org/jira/browse/LUCENE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500719
]
Steven Rowe commented on LUCENE-902:
This patch needs a small unit test showing that the problem exists, and that
[
https://issues.apache.org/jira/browse/LUCENE-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500715
]
Erik Hatcher commented on LUCENE-898:
-
It may still work ok, but my hunch is that changes to the QueryParser have
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project lucene-java has an issue affecting its community integration.
This issue affects
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project lucene-java has an issue affecting its community integration.
This issue affects
[
https://issues.apache.org/jira/browse/LUCENE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500634
]
Michael McCandless commented on LUCENE-887:
---
> > This actually means you can potentially have too many "lev
[
https://issues.apache.org/jira/browse/LUCENE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toru Matsuzawa updated LUCENE-902:
--
Attachment: (was: stopfilter.patch)
> Check on PositionIncrement with StopFilter.
> --
[
https://issues.apache.org/jira/browse/LUCENE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toru Matsuzawa updated LUCENE-902:
--
Attachment: stopfilter.patch
> Check on PositionIncrement with StopFilter.
> -
[
https://issues.apache.org/jira/browse/LUCENE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toru Matsuzawa updated LUCENE-902:
--
Attachment: stopfilter.patch
patch attached
> Check on PositionIncrement with StopFilter.
> -
Check on PositionIncrement with StopFilter.
Key: LUCENE-902
URL: https://issues.apache.org/jira/browse/LUCENE-902
Project: Lucene - Java
Issue Type: Bug
Components: Analysis
Affects
51 matches
Mail list logo
