[Lucene.Net] [jira] [Updated] (LUCENENET-434) Remove AnonymousXXXX classes to increase readablity
[ https://issues.apache.org/jira/browse/LUCENENET-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-434: Attachment: TeeSinkTokenFilter.patch I replaced the abstract method with a Func<>. Then used a anonymous constructor when creating a new instance. > Remove Anonymous classes to increase readablity > --- > > Key: LUCENENET-434 > URL: https://issues.apache.org/jira/browse/LUCENENET-434 > Project: Lucene.Net > Issue Type: Improvement > Components: Lucene.Net Core >Affects Versions: Lucene.Net 2.9.4g >Reporter: Scott Lombard >Assignee: Scott Lombard > Fix For: Lucene.Net 2.9.4g > > Attachments: TeeSinkTokenFilter.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > Replace Anonymous classes inhereted from JLCA which make the code > impossible to read. > Follow Digy's template to replace the single abstract method with Func<> or > Action<> > > like in FilterCache from: > protected abstract object MergeDeletes(IndexReader reader, object value); > to: > Func MergeDeletes; > > Determine a solution to the classes with more than 1 abstract method without > diverging much from Java. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Work started] (LUCENENET-434) Remove AnonymousXXXX classes to increase readablity
[ https://issues.apache.org/jira/browse/LUCENENET-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LUCENENET-434 started by Scott Lombard. > Remove Anonymous classes to increase readablity > --- > > Key: LUCENENET-434 > URL: https://issues.apache.org/jira/browse/LUCENENET-434 > Project: Lucene.Net > Issue Type: Improvement > Components: Lucene.Net Core >Affects Versions: Lucene.Net 2.9.4g >Reporter: Scott Lombard >Assignee: Scott Lombard > Fix For: Lucene.Net 2.9.4g > > Original Estimate: 168h > Remaining Estimate: 168h > > Replace Anonymous classes inhereted from JLCA which make the code > impossible to read. > Follow Digy's template to replace the single abstract method with Func<> or > Action<> > > like in FilterCache from: > protected abstract object MergeDeletes(IndexReader reader, object value); > to: > Func MergeDeletes; > > Determine a solution to the classes with more than 1 abstract method without > diverging much from Java. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Created] (LUCENENET-434) Remove AnonymousXXXX classes to increase readablity
Remove Anonymous classes to increase readablity --- Key: LUCENENET-434 URL: https://issues.apache.org/jira/browse/LUCENENET-434 Project: Lucene.Net Issue Type: Improvement Components: Lucene.Net Core Affects Versions: Lucene.Net 2.9.4g Reporter: Scott Lombard Assignee: Scott Lombard Fix For: Lucene.Net 2.9.4g Replace Anonymous classes inhereted from JLCA which make the code impossible to read. Follow Digy's template to replace the single abstract method with Func<> or Action<> like in FilterCache from: protected abstract object MergeDeletes(IndexReader reader, object value); to: Func MergeDeletes; Determine a solution to the classes with more than 1 abstract method without diverging much from Java. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-172) This patch fixes the unexceptional exceptions ecountered in FastCharStream and SupportClass
[ https://issues.apache.org/jira/browse/LUCENENET-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012760#comment-13012760 ] Scott Lombard commented on LUCENENET-172: - I am going to modify FastCharStream to include the functions ReadChar() and BeginToken() found in the patch. The original functions I will mark as obsolete to minimize the impact of the deviation from Java Lucene. > This patch fixes the unexceptional exceptions ecountered in FastCharStream > and SupportClass > --- > > Key: LUCENENET-172 > URL: https://issues.apache.org/jira/browse/LUCENENET-172 > Project: Lucene.Net > Issue Type: Improvement > Components: Lucene.Net Core >Affects Versions: Lucene.Net 2.3.1, Lucene.Net 2.3.2 >Reporter: Ben Martz >Assignee: Scott Lombard >Priority: Minor > Fix For: Lucene.Net 2.9.4 > > Attachments: lucene_2.3.1_exceptions_fix.patch > > > The java version of Lucene handles end-of-file in FastCharStream by throwing > an exception. This behavior has been ported to .NET but the behavior carries > an unacceptable cost in the .NET environment. This patch is based on the > prior work in LUCENENET-8 and LUCENENET-11, which I gratefully acknowledge > for the solution. While I understand that this patch is outside of the > current project specification in that it deviates from the "pure" nature of > the port, I believe that it is very important to make the patch available to > any developer looking to leverage Lucene.Net in their project. Thanks for > your consideration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Assigned] (LUCENENET-172) This patch fixes the unexceptional exceptions ecountered in FastCharStream and SupportClass
[ https://issues.apache.org/jira/browse/LUCENENET-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard reassigned LUCENENET-172: --- Assignee: Scott Lombard > This patch fixes the unexceptional exceptions ecountered in FastCharStream > and SupportClass > --- > > Key: LUCENENET-172 > URL: https://issues.apache.org/jira/browse/LUCENENET-172 > Project: Lucene.Net > Issue Type: Improvement > Components: Lucene.Net Core >Affects Versions: Lucene.Net 2.3.1, Lucene.Net 2.3.2 >Reporter: Ben Martz >Assignee: Scott Lombard >Priority: Minor > Fix For: Lucene.Net 2.9.4 > > Attachments: lucene_2.3.1_exceptions_fix.patch > > > The java version of Lucene handles end-of-file in FastCharStream by throwing > an exception. This behavior has been ported to .NET but the behavior carries > an unacceptable cost in the .NET environment. This patch is based on the > prior work in LUCENENET-8 and LUCENENET-11, which I gratefully acknowledge > for the solution. While I understand that this patch is outside of the > current project specification in that it deviates from the "pure" nature of > the port, I believe that it is very important to make the patch available to > any developer looking to leverage Lucene.Net in their project. Thanks for > your consideration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010051#comment-13010051 ] Scott Lombard commented on LUCENENET-380: - Why fork outside of ASF if we can keep it inside? Is a independent project justified? It seems to me there is a lot of infrastructure that needs to be duplicated and maintained. I agreed to starting a fork outside of ASF because I didn't think there was any possibility to bring code into lucene.net. Now, I just don't understand licensing well enough to rule out a dOCL license from db4o. > Evaluate Sharpen as a port tool > --- > > Key: LUCENENET-380 > URL: https://issues.apache.org/jira/browse/LUCENENET-380 > Project: Lucene.Net > Issue Type: Task > Components: Build Automation, Lucene.Net Contrib, Lucene.Net Core, > Lucene.Net Demo, Lucene.Net Test >Reporter: George Aroush >Assignee: Alex Thompson > Attachments: 3.0.2_JavaToCSharpConverter_AfterPostProcessing.zip, > 3.0.2_JavaToCSharpConverter_NoPostProcessing.zip, IndexWriter.java, > Lucene.Net.3_0_3_Sharpen20110106.zip, Lucene.Net.Sharpen20101104.zip, > Lucene.Net.Sharpen20101114.zip, NIOFSDirectory.java, QueryParser.java, > TestBufferedIndexInput.java, TestDateFilter.java > > > This task is to evaluate Sharpen as a port tool for Lucene.Net. > The files to be evaluated are attached. We need to run those files (which > are off Java Lucene 2.9.2) against Sharpen and compare the result against > JLCA result. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-380) Evaluate Sharpen as a port tool
[
https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009792#comment-13009792
]
Scott Lombard commented on LUCENENET-380:
-
I read the dOCL as one of three licensing options. From the dOCL:
{quote}You may obtain copies of the Software by download from the Versant
website. Software governed by this Agreement and Software governed by the GPL
are obtained from the same source. For this reason, portions of the Software
may be flagged as governed by the GPL license. However, the terms under which
Versant licenses the Software to you depend on your choice of license,
regardless of any GPL notices contained in the Software.{quote}
We are a FLOSS Application:
{quote}4. Free/Libre and Open Source Software Licenses
Where your FLOSS Application contains software components that were licensed
pursuant to one of the FLOSS licenses set forth below ("FLOSS Licenses"), you
may distribute such software components subject to that pre-existing FLOSS
License.
...
b. Apache Software License, versions 1.0, 1.1, or 2.0{quote}
I don't know if our fork will be Derived Software:
{quote}3. Derivative Works
For the purpose of this Agreement, software is deemed a derivative work of the
Software ("Derivative Work") where it is based on the Software, including
without limitation in the following circumstances:
a. the software is compiled against the Software;
b. the software contains specific references to the Software;
c. the software requires the Software to work; or
d. the software uses the proprietary API to the Software. {quote}
My concerns are more about the requirement to have a project link on the db4o
project website and who owns the changes to the sharpen.
To keep a GPL license we could not include it in the ASF repository. The GPL
license is acceptable for using the sharpen fork as build tool for Lucene.Net.
So the fork would become a separate project and I think would have to be
maintained independently of ASF.
What do other projects do?
> Evaluate Sharpen as a port tool
> ---
>
> Key: LUCENENET-380
> URL: https://issues.apache.org/jira/browse/LUCENENET-380
> Project: Lucene.Net
> Issue Type: Task
> Components: Build Automation, Lucene.Net Contrib, Lucene.Net Core,
> Lucene.Net Demo, Lucene.Net Test
>Reporter: George Aroush
>Assignee: Alex Thompson
> Attachments: 3.0.2_JavaToCSharpConverter_AfterPostProcessing.zip,
> 3.0.2_JavaToCSharpConverter_NoPostProcessing.zip, IndexWriter.java,
> Lucene.Net.3_0_3_Sharpen20110106.zip, Lucene.Net.Sharpen20101104.zip,
> Lucene.Net.Sharpen20101114.zip, NIOFSDirectory.java, QueryParser.java,
> TestBufferedIndexInput.java, TestDateFilter.java
>
>
> This task is to evaluate Sharpen as a port tool for Lucene.Net.
> The files to be evaluated are attached. We need to run those files (which
> are off Java Lucene 2.9.2) against Sharpen and compare the result against
> JLCA result.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Updated: (LUCENENET-399) Port changes from Java Lucene 2.9.3 and 2.9.4 releases
[ https://issues.apache.org/jira/browse/LUCENENET-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-399: Remaining Estimate: 40h (was: 0h) > Port changes from Java Lucene 2.9.3 and 2.9.4 releases > -- > > Key: LUCENENET-399 > URL: https://issues.apache.org/jira/browse/LUCENENET-399 > Project: Lucene.Net > Issue Type: Task > Components: Lucene.Net Core, Lucene.Net Test >Reporter: Troy Howard >Assignee: Scott Lombard > Fix For: Lucene.Net 2.9.4 > > Time Spent: 2h > Remaining Estimate: 40h > > Port changes from Java Lucene 2.9.3 and 2.9.4 releases. > The Lucene.Net 2.9.4 release will roll up the changes from both of those > releases into one. > Unit tests should be added or updated to reflect the changes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Work started: (LUCENENET-399) Port changes from Java Lucene 2.9.3 and 2.9.4 releases
[ https://issues.apache.org/jira/browse/LUCENENET-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LUCENENET-399 started by Scott Lombard. > Port changes from Java Lucene 2.9.3 and 2.9.4 releases > -- > > Key: LUCENENET-399 > URL: https://issues.apache.org/jira/browse/LUCENENET-399 > Project: Lucene.Net > Issue Type: Task > Components: Lucene.Net Core, Lucene.Net Test >Reporter: Troy Howard >Assignee: Scott Lombard > Fix For: Lucene.Net 2.9.4 > > > Port changes from Java Lucene 2.9.3 and 2.9.4 releases. > The Lucene.Net 2.9.4 release will roll up the changes from both of those > releases into one. > Unit tests should be added or updated to reflect the changes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Assigned: (LUCENENET-399) Port changes from Java Lucene 2.9.3 and 2.9.4 releases
[ https://issues.apache.org/jira/browse/LUCENENET-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard reassigned LUCENENET-399: --- Assignee: Scott Lombard > Port changes from Java Lucene 2.9.3 and 2.9.4 releases > -- > > Key: LUCENENET-399 > URL: https://issues.apache.org/jira/browse/LUCENENET-399 > Project: Lucene.Net > Issue Type: Task > Components: Lucene.Net Core, Lucene.Net Test >Reporter: Troy Howard >Assignee: Scott Lombard > Fix For: Lucene.Net 2.9.4 > > > Port changes from Java Lucene 2.9.3 and 2.9.4 releases. > The Lucene.Net 2.9.4 release will roll up the changes from both of those > releases into one. > Unit tests should be added or updated to reflect the changes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-372) NLS pack for Lucene.NET: BR, CJK, CN, CZ, DE, FR, NL, RU analyzers
[ https://issues.apache.org/jira/browse/LUCENENET-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-372: Component/s: Lucene.Net Contrib Labels: Analyzers (was: ) > NLS pack for Lucene.NET: BR, CJK, CN, CZ, DE, FR, NL, RU analyzers > -- > > Key: LUCENENET-372 > URL: https://issues.apache.org/jira/browse/LUCENENET-372 > Project: Lucene.Net > Issue Type: New Feature > Components: Lucene.Net Contrib >Reporter: Pasha Bizhan >Priority: Minor > Labels: Analyzers > Attachments: lucene-net-nls.zip > > > Port of java analyzers. Sorry for 1.4 version, it's from 2005 year -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-380: Component/s: Lucene.Net Test Lucene.Net Demo Lucene.Net Core Lucene.Net Contrib Due Date: 31/Dec/10 (was: 31/Dec/10) Fix Version/s: Lucene.Net 3.x > Evaluate Sharpen as a port tool > --- > > Key: LUCENENET-380 > URL: https://issues.apache.org/jira/browse/LUCENENET-380 > Project: Lucene.Net > Issue Type: Task > Components: Lucene.Net Contrib, Lucene.Net Core, Lucene.Net Demo, > Lucene.Net Test >Reporter: George Aroush > Fix For: Lucene.Net 3.x > > Attachments: 3.0.2_JavaToCSharpConverter_AfterPostProcessing.zip, > 3.0.2_JavaToCSharpConverter_NoPostProcessing.zip, IndexWriter.java, > Lucene.Net.3_0_3_Sharpen20110106.zip, Lucene.Net.Sharpen20101104.zip, > Lucene.Net.Sharpen20101114.zip, NIOFSDirectory.java, QueryParser.java, > TestBufferedIndexInput.java, TestDateFilter.java > > > This task is to evaluate Sharpen as a port tool for Lucene.Net. > The files to be evaluated are attached. We need to run those files (which > are off Java Lucene 2.9.2) against Sharpen and compare the result against > JLCA result. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-167) Compact Framework & Silverlight Support
[ https://issues.apache.org/jira/browse/LUCENENET-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-167: Component/s: Lucene.Net Test Lucene.Net Core Affects Version/s: (was: .NET API) > Compact Framework & Silverlight Support > --- > > Key: LUCENENET-167 > URL: https://issues.apache.org/jira/browse/LUCENENET-167 > Project: Lucene.Net > Issue Type: Wish > Components: Lucene.Net Core, Lucene.Net Test >Reporter: Andrew C. Smith >Priority: Trivial > Fix For: .NET API > > > Lucene.Net should support the Compact Framework & Silverlight versions of the > .NET Framework. > I've looked into what it might take to do this and most of it is pretty > trivial to be able to support these frameworks. Most of what this would take > is just changing the different type of classes to use for collection classes > used inside of Lucene.Net. > This does require changing some details in a lot of places, However this > should *not* bring any compatibility issues with *Java Lucene*'s API or index > format. It will just change the classes used to some different ones that the > frameworks support and also maybe need 1 to 3 classes that might need to be > implemented in Lucene.net itself. > Having made these changes Lucene.Net can be more available to new devices > such as running on a window mobile cell phone, or your pda, or run in a > Windows, Linux, or Mac computer that runs a silverlight application. This > will allow the .Net compact framework & silverlight developers to use > Lucene.Net in their applications to provide their users with the same > capabilities of an awesome search framework. Developers can also use > Lucene.Net to provide them spell checking capabilities in these environments. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-172) This patch fixes the unexceptional exceptions ecountered in FastCharStream and SupportClass
[ https://issues.apache.org/jira/browse/LUCENENET-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-172: Affects Version/s: (was: .NET API) Lucene.Net 2.3.1 Lucene.Net 2.3.2 > This patch fixes the unexceptional exceptions ecountered in FastCharStream > and SupportClass > --- > > Key: LUCENENET-172 > URL: https://issues.apache.org/jira/browse/LUCENENET-172 > Project: Lucene.Net > Issue Type: Improvement > Components: Lucene.Net Core >Affects Versions: Lucene.Net 2.3.1, Lucene.Net 2.3.2 >Reporter: Ben Martz >Priority: Minor > Fix For: .NET API > > Attachments: lucene_2.3.1_exceptions_fix.patch > > > The java version of Lucene handles end-of-file in FastCharStream by throwing > an exception. This behavior has been ported to .NET but the behavior carries > an unacceptable cost in the .NET environment. This patch is based on the > prior work in LUCENENET-8 and LUCENENET-11, which I gratefully acknowledge > for the solution. While I understand that this patch is outside of the > current project specification in that it deviates from the "pure" nature of > the port, I believe that it is very important to make the patch available to > any developer looking to leverage Lucene.Net in their project. Thanks for > your consideration. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-167) Compact Framework & Silverlight Support
[ https://issues.apache.org/jira/browse/LUCENENET-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-167: Priority: Trivial (was: Major) Affects Version/s: .NET API Fix Version/s: .NET API This is a great idea and the priority can be increased as the team has more time to implement. > Compact Framework & Silverlight Support > --- > > Key: LUCENENET-167 > URL: https://issues.apache.org/jira/browse/LUCENENET-167 > Project: Lucene.Net > Issue Type: Wish >Affects Versions: .NET API >Reporter: Andrew C. Smith >Priority: Trivial > Fix For: .NET API > > > Lucene.Net should support the Compact Framework & Silverlight versions of the > .NET Framework. > I've looked into what it might take to do this and most of it is pretty > trivial to be able to support these frameworks. Most of what this would take > is just changing the different type of classes to use for collection classes > used inside of Lucene.Net. > This does require changing some details in a lot of places, However this > should *not* bring any compatibility issues with *Java Lucene*'s API or index > format. It will just change the classes used to some different ones that the > frameworks support and also maybe need 1 to 3 classes that might need to be > implemented in Lucene.net itself. > Having made these changes Lucene.Net can be more available to new devices > such as running on a window mobile cell phone, or your pda, or run in a > Windows, Linux, or Mac computer that runs a silverlight application. This > will allow the .Net compact framework & silverlight developers to use > Lucene.Net in their applications to provide their users with the same > capabilities of an awesome search framework. Developers can also use > Lucene.Net to provide them spell checking capabilities in these environments. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-378) Objects with a Close method should support IDisposable
[ https://issues.apache.org/jira/browse/LUCENENET-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-378: Component/s: Lucene.Net Test Lucene.Net Demo Lucene.Net Core Affects Version/s: .NET API Fix Version/s: .NET API This is something that will be done with the implementation of the .NET API > Objects with a Close method should support IDisposable > -- > > Key: LUCENENET-378 > URL: https://issues.apache.org/jira/browse/LUCENENET-378 > Project: Lucene.Net > Issue Type: Improvement > Components: Lucene.Net Core, Lucene.Net Demo, Lucene.Net Test >Affects Versions: .NET API > Environment: .NET >Reporter: Kelly Elias > Fix For: .NET API > > > It would be very useful to have objects such as IndexSearcher and Directory > support IDisposable. Then users can use "using" blocks to manage the lifespan > of the objects and don't need to worry about accidentally leaving such > objects open. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-172) This patch fixes the unexceptional exceptions ecountered in FastCharStream and SupportClass
[ https://issues.apache.org/jira/browse/LUCENENET-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-172: Component/s: Lucene.Net Core Priority: Minor (was: Major) Affects Version/s: .NET API Fix Version/s: .NET API This was originally a improvement made for an earlier release I haven't looked at the code to see if it is still relevant. If it is it should be incorporated into the .net API. > This patch fixes the unexceptional exceptions ecountered in FastCharStream > and SupportClass > --- > > Key: LUCENENET-172 > URL: https://issues.apache.org/jira/browse/LUCENENET-172 > Project: Lucene.Net > Issue Type: Improvement > Components: Lucene.Net Core >Affects Versions: .NET API >Reporter: Ben Martz >Priority: Minor > Fix For: .NET API > > Attachments: lucene_2.3.1_exceptions_fix.patch > > > The java version of Lucene handles end-of-file in FastCharStream by throwing > an exception. This behavior has been ported to .NET but the behavior carries > an unacceptable cost in the .NET environment. This patch is based on the > prior work in LUCENENET-8 and LUCENENET-11, which I gratefully acknowledge > for the solution. While I understand that this patch is outside of the > current project specification in that it deviates from the "pure" nature of > the port, I believe that it is very important to make the patch available to > any developer looking to leverage Lucene.Net in their project. Thanks for > your consideration. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (LUCENENET-394) AnonymousClassScoreDocComparator throws nullreferenceexception
[
https://issues.apache.org/jira/browse/LUCENENET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Lombard resolved LUCENENET-394.
-
Resolution: Won't Fix
Assignee: Scott Lombard
I changed the priority on this item to minor. I am going to wait a few days
before closing it to get a feel for what the community wants to do about bugs
pre 2.9.2.
> AnonymousClassScoreDocComparator throws nullreferenceexception
> --
>
> Key: LUCENENET-394
> URL: https://issues.apache.org/jira/browse/LUCENENET-394
> Project: Lucene.Net
> Issue Type: Bug
> Environment: Lucene.NET 2.4.0.2
>Reporter: Jaap Taal
>Assignee: Scott Lombard
>Priority: Minor
> Labels: exception, fieldcache, sort,
>
> I've added a field to my index (Store.NO, Index.UN_TOKENIZED), I've updated a
> couple of my documents and I'm now sorting on it (after I collected document
> id's in a HitCollector). My search results in some documents that consist of
> document with the field and without.
> I use a simple implementation of SortComparator which implements
> GetComparable by just returning the passed termtext.
> I've set a breakpoint at my GetComparable method and I see the correct values
> (the method is NOT called for documents that don't have the field as a value).
> When SortComparer.Compare is called, a NullReferenceException occurs in:
> {code}
> public virtual int Compare(ScoreDoc i, ScoreDoc j)
> {
> return this.cachedValues[i.doc].CompareTo(this.cachedValues[j.doc]);
> }
> {code}
> The expression this.cachedValues[i.doc] is null.
> Is this a limitation of SortComparer (and its
> AnonymousClassScoreDocComparator) that all documents in a searchresult need
> to have a value for the field??
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-394) AnonymousClassScoreDocComparator throws nullreferenceexception
[
https://issues.apache.org/jira/browse/LUCENENET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Lombard updated LUCENENET-394:
Priority: Minor (was: Blocker)
> AnonymousClassScoreDocComparator throws nullreferenceexception
> --
>
> Key: LUCENENET-394
> URL: https://issues.apache.org/jira/browse/LUCENENET-394
> Project: Lucene.Net
> Issue Type: Bug
> Environment: Lucene.NET 2.4.0.2
>Reporter: Jaap Taal
>Priority: Minor
> Labels: exception, fieldcache, sort,
>
> I've added a field to my index (Store.NO, Index.UN_TOKENIZED), I've updated a
> couple of my documents and I'm now sorting on it (after I collected document
> id's in a HitCollector). My search results in some documents that consist of
> document with the field and without.
> I use a simple implementation of SortComparator which implements
> GetComparable by just returning the passed termtext.
> I've set a breakpoint at my GetComparable method and I see the correct values
> (the method is NOT called for documents that don't have the field as a value).
> When SortComparer.Compare is called, a NullReferenceException occurs in:
> {code}
> public virtual int Compare(ScoreDoc i, ScoreDoc j)
> {
> return this.cachedValues[i.doc].CompareTo(this.cachedValues[j.doc]);
> }
> {code}
> The expression this.cachedValues[i.doc] is null.
> Is this a limitation of SortComparer (and its
> AnonymousClassScoreDocComparator) that all documents in a searchresult need
> to have a value for the field??
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-382) Create a wiki page for Lucene.Net
[ https://issues.apache.org/jira/browse/LUCENENET-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-382: Component/s: Project Infrastructure Affects Version/s: .NET API Lucene.Net 3.x Lucene.Net 2.9.4 Lucene.Net 2.9.2 Fix Version/s: Graduate Remaining Estimate: 12h Original Estimate: 12h > Create a wiki page for Lucene.Net > - > > Key: LUCENENET-382 > URL: https://issues.apache.org/jira/browse/LUCENENET-382 > Project: Lucene.Net > Issue Type: Task > Components: Project Infrastructure >Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4, Lucene.Net 3.x, .NET > API >Reporter: George Aroush > Fix For: Graduate > > Original Estimate: 12h > Remaining Estimate: 12h > > We need to create a wiki page for Lucene.Net with how-to's and all. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-389) Signing the released assembly
[ https://issues.apache.org/jira/browse/LUCENENET-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-389: Component/s: Lucene.Net Core Due Date: 28/Feb/11 Priority: Critical (was: Major) Affects Version/s: Lucene.Net 2.9.2 Fix Version/s: Lucene.Net 2.9.2 Issue Type: Improvement (was: Wish) Remaining Estimate: 16h Original Estimate: 16h > Signing the released assembly > - > > Key: LUCENENET-389 > URL: https://issues.apache.org/jira/browse/LUCENENET-389 > Project: Lucene.Net > Issue Type: Improvement > Components: Lucene.Net Core >Affects Versions: Lucene.Net 2.9.2 >Reporter: Patric Forsgard >Priority: Critical > Fix For: Lucene.Net 2.9.2 > > Original Estimate: 16h > Remaining Estimate: 16h > > In the project I working in i need a signed version of the > Lucene.Net-assembly. For the moment I will compile and sign with my own key > but it would be great if the official release already should be signed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-398) Prepare the code for ingestion
[ https://issues.apache.org/jira/browse/LUCENENET-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-398: Assignee: Sergey Mirvoda > Prepare the code for ingestion > -- > > Key: LUCENENET-398 > URL: https://issues.apache.org/jira/browse/LUCENENET-398 > Project: Lucene.Net > Issue Type: Sub-task > Components: Lucene.Net Contrib >Reporter: Scott Lombard >Assignee: Sergey Mirvoda > > Prepare source to be imported in the Lucene.Net respository -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (LUCENENET-398) Prepare the code for ingestion
Prepare the code for ingestion -- Key: LUCENENET-398 URL: https://issues.apache.org/jira/browse/LUCENENET-398 Project: Lucene.Net Issue Type: Sub-task Components: Lucene.Net Contrib Reporter: Scott Lombard Prepare source to be imported in the Lucene.Net respository -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (LUCENENET-397) Resolution of the legal issues
Resolution of the legal issues -- Key: LUCENENET-397 URL: https://issues.apache.org/jira/browse/LUCENENET-397 Project: Lucene.Net Issue Type: Sub-task Reporter: Scott Lombard Assignee: Troy Howard Priority: Blocker Resolution of the legal issues around ingesting the code into Lucene.Net -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (LUCENENET-391) Luke.Net for Lucene.Net
[ https://issues.apache.org/jira/browse/LUCENENET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996708#comment-12996708 ] Scott Lombard commented on LUCENENET-391: - Public fork of Luke.Net on bitbucket as a staging area to prepare the code for ingestion. Waiting on Licensing issues to be resolved. > Luke.Net for Lucene.Net > --- > > Key: LUCENENET-391 > URL: https://issues.apache.org/jira/browse/LUCENENET-391 > Project: Lucene.Net > Issue Type: New Feature > Components: Lucene.Net Contrib >Affects Versions: Lucene.Net 2.9.2 >Reporter: Pasha Bizhan >Priority: Minor > Labels: Luke.Net > Attachments: luke-net-bin.zip, luke-net-src.zip > > > .net port of Luke.Net for Lucene.Net -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-391) Luke.Net for Lucene.Net
[ https://issues.apache.org/jira/browse/LUCENENET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-391: Component/s: Lucene.Net Contrib Description: .net port of Luke.Net for Lucene.Net (was: .net port of Luke.Net for Lucene.Net 1.4) Affects Version/s: Lucene.Net 2.9.2 Labels: Luke.Net (was: ) > Luke.Net for Lucene.Net > --- > > Key: LUCENENET-391 > URL: https://issues.apache.org/jira/browse/LUCENENET-391 > Project: Lucene.Net > Issue Type: New Feature > Components: Lucene.Net Contrib >Affects Versions: Lucene.Net 2.9.2 >Reporter: Pasha Bizhan >Priority: Minor > Labels: Luke.Net > Attachments: luke-net-bin.zip, luke-net-src.zip > > > .net port of Luke.Net for Lucene.Net -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (LUCENENET-393) Lucene - Search Engine for .net Issue
[ https://issues.apache.org/jira/browse/LUCENENET-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard closed LUCENENET-393. --- Resolution: Cannot Reproduce Assignee: Scott Lombard This is more of a question than Issue. If more detailed information on the problem is presented this issue can be reopened > Lucene - Search Engine for .net Issue > - > > Key: LUCENENET-393 > URL: https://issues.apache.org/jira/browse/LUCENENET-393 > Project: Lucene.Net > Issue Type: Bug > Environment: Win server 2003 SP2,.net 3.5 with sp1,AMD processor 2 > GHz 4GB RAM >Reporter: Rahul Panwar >Assignee: Scott Lombard >Priority: Blocker > > We have implemented the Lucene.net for site search. We have implemented this > in following steps: > 1.Processing index from Database (around 4 million records are in DB) to > file system. > 2.Implement search on indexed file. > It's working fine for us and results are very fast in development environment > but when we have published this to production server is getting slow and > process "w3wp.exe" taking 40-50% CPU continuously. We have implemented this > for two applications and in this case 100% CPU utilized by "w3wp.exe". > Please suggest if there is any workaround for this issue? OR also let us know > if it's a known issue in Lucene? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-377) Upgrade solution to VS2010
[ https://issues.apache.org/jira/browse/LUCENENET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-377: Component/s: Lucene.Net Core Affects Version/s: .NET API Lucene.Net 3.x Lucene.Net 2.9.4 Lucene.Net 2.9.2 Fix Version/s: Lucene.Net 2.9.2 Assignee: Prescott Nasser Labels: solution (was: ) Remaining Estimate: 10m Original Estimate: 10m > Upgrade solution to VS2010 > -- > > Key: LUCENENET-377 > URL: https://issues.apache.org/jira/browse/LUCENENET-377 > Project: Lucene.Net > Issue Type: Task > Components: Lucene.Net Core >Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4, Lucene.Net 3.x, .NET > API >Reporter: Jeffrey Cameron >Assignee: Prescott Nasser > Labels: solution > Fix For: Lucene.Net 2.9.2 > > Attachments: lucene.zip > > Original Estimate: 10m > Remaining Estimate: 10m > > VS2005 is quite out of date now and there are many new improvements in > VS2010. You can still leave the framework support at .NET 2.0 if you like. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-379) Clean up Lucene.Net website
[ https://issues.apache.org/jira/browse/LUCENENET-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-379: Fix Version/s: Graduate > Clean up Lucene.Net website > --- > > Key: LUCENENET-379 > URL: https://issues.apache.org/jira/browse/LUCENENET-379 > Project: Lucene.Net > Issue Type: Task > Components: Project Infrastructure >Reporter: George Aroush >Assignee: Troy Howard > Labels: Website > Fix For: Graduate > > Attachments: Lucene.zip, New Logo Idea.jpg, asfcms.zip, asfcms_1.patch > > Original Estimate: 80h > Remaining Estimate: 80h > > The existing Lucene.Net home page at http://lucene.apache.org/lucene.net/ is > still based on the incubation, out of date design. This JIRA task is to > bring it up to date with other ASF project's web page. > The existing website is here: > https://svn.apache.org/repos/asf/lucene/lucene.net/site/ > See http://www.apache.org/dev/project-site.html to get started. > It would be best to start by cloning an existing ASF project's website and > adopting it for Lucene.Net. Some examples, > https://svn.apache.org/repos/asf/lucene/pylucene/site/ and > https://svn.apache.org/repos/asf/lucene/java/site/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-379) Clean up Lucene.Net website
[ https://issues.apache.org/jira/browse/LUCENENET-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-379: Remaining Estimate: 80h (was: 336h) Original Estimate: 80h (was: 336h) > Clean up Lucene.Net website > --- > > Key: LUCENENET-379 > URL: https://issues.apache.org/jira/browse/LUCENENET-379 > Project: Lucene.Net > Issue Type: Task > Components: Project Infrastructure >Reporter: George Aroush >Assignee: Troy Howard > Labels: Website > Attachments: Lucene.zip, New Logo Idea.jpg, asfcms.zip, asfcms_1.patch > > Original Estimate: 80h > Remaining Estimate: 80h > > The existing Lucene.Net home page at http://lucene.apache.org/lucene.net/ is > still based on the incubation, out of date design. This JIRA task is to > bring it up to date with other ASF project's web page. > The existing website is here: > https://svn.apache.org/repos/asf/lucene/lucene.net/site/ > See http://www.apache.org/dev/project-site.html to get started. > It would be best to start by cloning an existing ASF project's website and > adopting it for Lucene.Net. Some examples, > https://svn.apache.org/repos/asf/lucene/pylucene/site/ and > https://svn.apache.org/repos/asf/lucene/java/site/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-379) Clean up Lucene.Net website
[ https://issues.apache.org/jira/browse/LUCENENET-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Lombard updated LUCENENET-379: Component/s: Project Infrastructure Due Date: 28/Feb/11 (was: 31/Dec/10) Assignee: Troy Howard Labels: Website (was: ) Remaining Estimate: 336h Original Estimate: 336h > Clean up Lucene.Net website > --- > > Key: LUCENENET-379 > URL: https://issues.apache.org/jira/browse/LUCENENET-379 > Project: Lucene.Net > Issue Type: Task > Components: Project Infrastructure >Reporter: George Aroush >Assignee: Troy Howard > Labels: Website > Attachments: Lucene.zip, New Logo Idea.jpg, asfcms.zip, asfcms_1.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > The existing Lucene.Net home page at http://lucene.apache.org/lucene.net/ is > still based on the incubation, out of date design. This JIRA task is to > bring it up to date with other ASF project's web page. > The existing website is here: > https://svn.apache.org/repos/asf/lucene/lucene.net/site/ > See http://www.apache.org/dev/project-site.html to get started. > It would be best to start by cloning an existing ASF project's website and > adopting it for Lucene.Net. Some examples, > https://svn.apache.org/repos/asf/lucene/pylucene/site/ and > https://svn.apache.org/repos/asf/lucene/java/site/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (LUCENENET-379) Clean up Lucene.Net website
[ https://issues.apache.org/jira/browse/LUCENENET-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996239#comment-12996239 ] Scott Lombard commented on LUCENENET-379: - I like the idea of the a new logo. A logo design contest sounds like a good idea to me. > Clean up Lucene.Net website > --- > > Key: LUCENENET-379 > URL: https://issues.apache.org/jira/browse/LUCENENET-379 > Project: Lucene.Net > Issue Type: Task >Reporter: George Aroush > Attachments: Lucene.zip, New Logo Idea.jpg, asfcms.zip, asfcms_1.patch > > > The existing Lucene.Net home page at http://lucene.apache.org/lucene.net/ is > still based on the incubation, out of date design. This JIRA task is to > bring it up to date with other ASF project's web page. > The existing website is here: > https://svn.apache.org/repos/asf/lucene/lucene.net/site/ > See http://www.apache.org/dev/project-site.html to get started. > It would be best to start by cloning an existing ASF project's website and > adopting it for Lucene.Net. Some examples, > https://svn.apache.org/repos/asf/lucene/pylucene/site/ and > https://svn.apache.org/repos/asf/lucene/java/site/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
