[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839141#action_12839141 ] Michael Garski commented on LUCENENET-345: -- I should add that the TermsFilter and BooleanFilter are ports of the Java contrib filters. I don't have any comments in them attributing the original source, but will ensure such comments are added prior to committing. My intention is to add more items to the Lucene.Extensions project including TokenFilters and Tokenizers once I've completed our 2.9 migration. > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345 Extensions.patch > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[
https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839194#action_12839194
]
Digy commented on LUCENENET-345:
Hi Mike,
Is WeakKey.Equals correct? (At the end of your patch)
{code}
public override bool Equals(object obj)
{
if (obj is WeakKey)
{
return ((WeakKey)obj).GetHashCode().Equals(this.GetHashCode());
}
return false;
}
{code}
Shouldn't it be something like
{code}
return ((WeakKey)obj).Target.Equals(this.Target); //maybe some null controls
{code} ?
DIGY
> [Contrib] Extensions
>
>
> Key: LUCENENET-345
> URL: https://issues.apache.org/jira/browse/LUCENENET-345
> Project: Lucene.Net
> Issue Type: New Feature
>Reporter: Michael Garski
> Attachments: LUCENENET-345 Extensions.patch
>
>
> I have created a few generic extensions to Lucene.Net that I use quiet a bit.
> It's packaged up as a VS2008 solution with two projects. The test project
> is a Visual Studio test project as opposed to NUnit, and that can be changed.
> Here is a summary of the contents:
> FieldEnumerators : provides foreach syntax support when enumerating over all
> of the terms in the index.
> TermVectorEnumerator : provides foreach syntax to allow for enumerating over
> all of the term vectors in an index.
> BooleanFilter : combine multiple query filters in various logical
> combinations.
> TermsFilter : creates a filter from several terms as a logical OR.
> SegmentCache : a generic cache that works with the segment-level searching in
> Lucene 2.9 to cache any data at the segment level in the same manner as the
> field cache and CachingWrapperFilter which I've used for caching aggregate
> data on the documents in a segment for use in diagnostics and for caching
> TermVectors.
> SegmentsGenCommit : adds the ability to open an index from the version
> specified in the segments file as opposed to inferring the version from the
> files in the index directory.
> Refer to the documentation comments and unit tests for how to use the items.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839270#action_12839270 ] Michael Garski commented on LUCENENET-345: -- Good point - I'll clean that up and re-post the patch. > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345 Extensions.patch > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839274#action_12839274 ] Digy commented on LUCENENET-345: Hi Mike, I am using VS 2008 express edition at home and VS unit test is not available. I would like Nunit for testing. DIGY > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345 Extensions.patch > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[
https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839286#action_12839286
]
Digy commented on LUCENENET-345:
Sorry for disturbance but
{code}
if (this.Target != null && other.Target != null)
{
return this.Target.Equals(other.Target);
}
{code}
may fail, since this.Target in "if" can turn to null before return-statement is
executed. That would result in NullReferenceException.
You have to make hard refs to "Target"s before using them.
DIGY
> [Contrib] Extensions
>
>
> Key: LUCENENET-345
> URL: https://issues.apache.org/jira/browse/LUCENENET-345
> Project: Lucene.Net
> Issue Type: New Feature
>Reporter: Michael Garski
> Attachments: LUCENENET-345 Extensions.patch, LUCENENET-345 V2.patch
>
>
> I have created a few generic extensions to Lucene.Net that I use quiet a bit.
> It's packaged up as a VS2008 solution with two projects. The test project
> is a Visual Studio test project as opposed to NUnit, and that can be changed.
> Here is a summary of the contents:
> FieldEnumerators : provides foreach syntax support when enumerating over all
> of the terms in the index.
> TermVectorEnumerator : provides foreach syntax to allow for enumerating over
> all of the term vectors in an index.
> BooleanFilter : combine multiple query filters in various logical
> combinations.
> TermsFilter : creates a filter from several terms as a logical OR.
> SegmentCache : a generic cache that works with the segment-level searching in
> Lucene 2.9 to cache any data at the segment level in the same manner as the
> field cache and CachingWrapperFilter which I've used for caching aggregate
> data on the documents in a segment for use in diagnostics and for caching
> TermVectors.
> SegmentsGenCommit : adds the ability to open an index from the version
> specified in the segments file as opposed to inferring the version from the
> files in the index directory.
> Refer to the documentation comments and unit tests for how to use the items.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839288#action_12839288 ] Michael Garski commented on LUCENENET-345: -- Thanks for the feedback! I'll take more precautions in that method when I move the tests over to NUnit. > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345 Extensions.patch, LUCENENET-345 V2.patch > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839320#action_12839320 ] Digy commented on LUCENENET-345: Shortly, It would be good if we had a port of https://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/contrib/queries DIGY > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345 Extensions.patch, LUCENENET-345 V2.patch, > Queries.Net.rar > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839339#action_12839339 ] Michael Garski commented on LUCENENET-345: -- DIGY - Moving the filters to another project is not feasible as the TermsFilter uses the FieldEnumerators and I don't think interdependencies between contrib projects is a good idea. The project I contributed is an entire piece of functionality that is not intended to be broken up which I will continue to maintain and add on to. Creating projects and test projects for every two or three classes is not feasible and increases the overhead of maintaining them. Additionally, I don't think there is any reason to follow the same directory layout as the Java contrib section as it serves as a place to share functionality that has been created and contributed. Michael > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345 Extensions.patch, LUCENENET-345 V2.patch, > Queries.Net.rar > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839502#action_12839502 ] Digy commented on LUCENENET-345: Hi Mike, Since I used Similarity.Net in my old projects and it is in contrib/queries now, I started to port java's "contrib/queries" as "Queries.Net". I plan to open an issue about that soon. Where do you think BooleanFilter and TermsFilter should go? Should I leave them as unimplemeted and refer to your contrib? Would that be good? DIGY > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345 Extensions.patch, LUCENENET-345 V2.patch, > Queries.Net.rar > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839728#action_12839728 ] Michael Garski commented on LUCENENET-345: -- DIGY, Great to see you are have a few items for the contrib section as well! My thought is that many of the small items in contrib such as analyzers, filters - items that consist of no more than a few classes and their respective tests - be combined into one project. Larger pieces of functionality such as the highlighter would remain in their respective projects. Perhaps we should combine our two contributions into one project? Michael > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345 Extensions.patch, LUCENENET-345 V2.patch, > Queries.Net.rar > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839797#action_12839797 ] Digy commented on LUCENENET-345: bq. Great to see you are have a few items for the contrib section as well! https://issues.apache.org/jira/browse/LUCENENET-342 bq. My thought is that many of the small items in contrib such as analyzers, filters - items that consist of no more than a few classes and their respective tests - be combined into one project. Larger pieces of functionality such as the highlighter would remain in their respective projects. Since Lucene.Net lacks good documentation, people could find the necessary package (or search for contribs ported) easily if we kept the same structure. On the other hand, we can can gather all Lucene.Net specifics codes under a single project and have a global solution that compiles all contribs and their test cases. bq. Perhaps we should combine our two contributions into one project? Under which name? Just looking at its name, will people know that it is a port from Java( or Lucene.Net specific code)? DIGY > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345 Extensions.patch, LUCENENET-345 V2.patch, > Queries.Net.rar > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839960#action_12839960 ] Michael Garski commented on LUCENENET-345: -- I'll remove the BooleanFilter & TermsFilter from my contribution as if the goal is to keep partity between ported contrib libraries they really belong in Queries.Net. We could then use the Extensions project as a place for all of the Lucene.Net specific items. Any thoughts on that? > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345 Extensions.patch, LUCENENET-345 V2.patch, > Queries.Net.rar > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[
https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840223#action_12840223
]
Digy commented on LUCENENET-345:
{quote}
I'll remove the BooleanFilter & TermsFilter from my contribution as if the goal
is to keep partity between ported contrib libraries they really belong in
Queries.Net.
We could then use the Extensions project as a place for all of the Lucene.Net
specific items.
{quote}
+1
> [Contrib] Extensions
>
>
> Key: LUCENENET-345
> URL: https://issues.apache.org/jira/browse/LUCENENET-345
> Project: Lucene.Net
> Issue Type: New Feature
>Reporter: Michael Garski
> Attachments: LUCENENET-345 Extensions.patch, LUCENENET-345 V2.patch,
> Queries.Net.rar
>
>
> I have created a few generic extensions to Lucene.Net that I use quiet a bit.
> It's packaged up as a VS2008 solution with two projects. The test project
> is a Visual Studio test project as opposed to NUnit, and that can be changed.
> Here is a summary of the contents:
> FieldEnumerators : provides foreach syntax support when enumerating over all
> of the terms in the index.
> TermVectorEnumerator : provides foreach syntax to allow for enumerating over
> all of the term vectors in an index.
> BooleanFilter : combine multiple query filters in various logical
> combinations.
> TermsFilter : creates a filter from several terms as a logical OR.
> SegmentCache : a generic cache that works with the segment-level searching in
> Lucene 2.9 to cache any data at the segment level in the same manner as the
> field cache and CachingWrapperFilter which I've used for caching aggregate
> data on the documents in a segment for use in diagnostics and for caching
> TermVectors.
> SegmentsGenCommit : adds the ability to open an index from the version
> specified in the segments file as opposed to inferring the version from the
> files in the index directory.
> Refer to the documentation comments and unit tests for how to use the items.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841562#action_12841562 ] Digy commented on LUCENENET-345: Hi Mike, I think there is a misunderstanding. I haven't ported BooleanFilter & TermsFilter to avoid duplicate work. Can you integrate them into LUCENENET-347 (which is already in trunk) ? DIGY > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345-Contrib-Net.patch > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841564#action_12841564 ] Michael Garski commented on LUCENENET-345: -- Gotcha :) I'll add them and create a patch then tag it to LUCENENET-347. > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345-Contrib-Net.patch > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842732#action_12842732 ] Michael Garski commented on LUCENENET-345: -- Any feedback on the patch? If not I'll go ahead and commit it to the contrib section. Michael > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345-Contrib-Net.patch > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-345) [Contrib] Extensions
[ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842738#action_12842738 ] Digy commented on LUCENENET-345: Go ahead Michael. Here are the two analyzers I mostly use. http://people.apache.org/~digy/lucene.net/Analysis.Ext.rar Maybe we can think to include them in this project after your commit. DIGY > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345-Contrib-Net.patch > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: [jira] Commented: (LUCENENET-345) [Contrib] Extensions
Committed. I'm open to any and all additions to the Contrib.Net project! Michael -Original Message- From: Digy (JIRA) [mailto:j...@apache.org] Sent: Monday, March 08, 2010 9:15 AM To: lucene-net-dev@lucene.apache.org Subject: [jira] Commented: (LUCENENET-345) [Contrib] Extensions [ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842738#action_12842738 ] Digy commented on LUCENENET-345: Go ahead Michael. Here are the two analyzers I mostly use. http://people.apache.org/~digy/lucene.net/Analysis.Ext.rar Maybe we can think to include them in this project after your commit. DIGY > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345-Contrib-Net.patch > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: [jira] Commented: (LUCENENET-345) [Contrib] Extensions
Added to Contrib.Net. DIGY -Original Message- From: Michael Garski [mailto:mgar...@myspace-inc.com] Sent: Monday, March 08, 2010 7:38 PM To: lucene-net-dev@lucene.apache.org Subject: RE: [jira] Commented: (LUCENENET-345) [Contrib] Extensions Committed. I'm open to any and all additions to the Contrib.Net project! Michael -Original Message- From: Digy (JIRA) [mailto:j...@apache.org] Sent: Monday, March 08, 2010 9:15 AM To: lucene-net-dev@lucene.apache.org Subject: [jira] Commented: (LUCENENET-345) [Contrib] Extensions [ https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842738#action_12842738 ] Digy commented on LUCENENET-345: Go ahead Michael. Here are the two analyzers I mostly use. http://people.apache.org/~digy/lucene.net/Analysis.Ext.rar Maybe we can think to include them in this project after your commit. DIGY > [Contrib] Extensions > > > Key: LUCENENET-345 > URL: https://issues.apache.org/jira/browse/LUCENENET-345 > Project: Lucene.Net > Issue Type: New Feature >Reporter: Michael Garski > Attachments: LUCENENET-345-Contrib-Net.patch > > > I have created a few generic extensions to Lucene.Net that I use quiet a bit. > It's packaged up as a VS2008 solution with two projects. The test project > is a Visual Studio test project as opposed to NUnit, and that can be changed. > Here is a summary of the contents: > FieldEnumerators : provides foreach syntax support when enumerating over all > of the terms in the index. > TermVectorEnumerator : provides foreach syntax to allow for enumerating over > all of the term vectors in an index. > BooleanFilter : combine multiple query filters in various logical > combinations. > TermsFilter : creates a filter from several terms as a logical OR. > SegmentCache : a generic cache that works with the segment-level searching in > Lucene 2.9 to cache any data at the segment level in the same manner as the > field cache and CachingWrapperFilter which I've used for caching aggregate > data on the documents in a segment for use in diagnostics and for caching > TermVectors. > SegmentsGenCommit : adds the ability to open an index from the version > specified in the segments file as opposed to inferring the version from the > files in the index directory. > Refer to the documentation comments and unit tests for how to use the items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
