[jira] Commented: (LUCENE-1482) Replace infoSteram by a logging framework (SLF4J)
[
https://issues.apache.org/jira/browse/LUCENE-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854919#action_12854919
]
Jukka Zitting commented on LUCENE-1482:
---
We use SLF4J in Jackrabbit, and having logs from the embedded Lucene index
available through the same mechanism would be quite useful in some situations.
BTW, using isDebugEnabled() is often not necessary with SLF4J, see
http://www.slf4j.org/faq.html#logging_performance
> Replace infoSteram by a logging framework (SLF4J)
> -
>
> Key: LUCENE-1482
> URL: https://issues.apache.org/jira/browse/LUCENE-1482
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
>Reporter: Shai Erera
> Fix For: 3.1
>
> Attachments: LUCENE-1482-2.patch, LUCENE-1482.patch,
> slf4j-api-1.5.6.jar, slf4j-nop-1.5.6.jar
>
>
> Lucene makes use of infoStream to output messages in its indexing code only.
> For debugging purposes, when the search application is run on the customer
> side, getting messages from other code flows, like search, query parsing,
> analysis etc can be extremely useful.
> There are two main problems with infoStream today:
> 1. It is owned by IndexWriter, so if I want to add logging capabilities to
> other classes I need to either expose an API or propagate infoStream to all
> classes (see for example DocumentsWriter, which receives its infoStream
> instance from IndexWriter).
> 2. I can either turn debugging on or off, for the entire code.
> Introducing a logging framework can allow each class to control its logging
> independently, and more importantly, allows the application to turn on
> logging for only specific areas in the code (i.e., org.apache.lucene.index.*).
> I've investigated SLF4J (stands for Simple Logging Facade for Java) which is,
> as it names states, a facade over different logging frameworks. As such, you
> can include the slf4j.jar in your application, and it recognizes at deploy
> time what is the actual logging framework you'd like to use. SLF4J comes with
> several adapters for Java logging, Log4j and others. If you know your
> application uses Java logging, simply drop slf4j.jar and slf4j-jdk14.jar in
> your classpath, and your logging statements will use Java logging underneath
> the covers.
> This makes the logging code very simple. For a class A the logger will be
> instantiated like this:
> public class A {
> private static final logger = LoggerFactory.getLogger(A.class);
> }
> And will later be used like this:
> public class A {
> private static final logger = LoggerFactory.getLogger(A.class);
> public void foo() {
> if (logger.isDebugEnabled()) {
> logger.debug("message");
> }
> }
> }
> That's all !
> Checking for isDebugEnabled is very quick, at least using the JDK14 adapter
> (but I assume it's fast also over other logging frameworks).
> The important thing is, every class controls its own logger. Not all classes
> have to output logging messages, and we can improve Lucene's logging
> gradually, w/o changing the API, by adding more logging messages to
> interesting classes.
> I will submit a patch shortly
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
[jira] Created: (LUCENE-1675) Add a link to the release archive
Add a link to the release archive - Key: LUCENE-1675 URL: https://issues.apache.org/jira/browse/LUCENE-1675 Project: Lucene - Java Issue Type: Improvement Components: Website Reporter: Jukka Zitting Priority: Minor It would be nice if the [Releases page|http://lucene.apache.org/java/docs/releases.html] contained a link to the release archive at http://archive.apache.org/dist/lucene/java/. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
[jira] Commented: (LUCENE-931) Some files are missing the license headers
[ https://issues.apache.org/jira/browse/LUCENE-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503034 ] Jukka Zitting commented on LUCENE-931: -- Nice, thanks! > Some files are missing the license headers > -- > > Key: LUCENE-931 > URL: https://issues.apache.org/jira/browse/LUCENE-931 > Project: Lucene - Java > Issue Type: Wish > Components: Javadocs >Reporter: Michael Busch >Assignee: Michael Busch >Priority: Trivial > Fix For: 2.2 > > Attachments: lucene-931.patch > > > Jukka provided the following list of files that are missing the license > headers. > In addition there might be other files (like build scripts) that don't have > the headers. > src/java/org/apache/lucene/document/MapFieldSelector.java > src/java/org/apache/lucene/search/PrefixFilter.java > src/test/org/apache/lucene/TestHitIterator.java > src/test/org/apache/lucene/analysis/TestISOLatin1AccentFilter.java > src/test/org/apache/lucene/index/TestAddIndexesNoOptimize.java > src/test/org/apache/lucene/index/TestBackwardsCompatibility.java > src/test/org/apache/lucene/index/TestFieldInfos.java > src/test/org/apache/lucene/index/TestIndexFileDeleter.java > src/test/org/apache/lucene/index/TestIndexWriter.java > src/test/org/apache/lucene/index/TestIndexWriterDelete.java > src/test/org/apache/lucene/index/TestIndexWriterLockRelease.java > src/test/org/apache/lucene/index/TestIndexWriterMergePolicy.java > src/test/org/apache/lucene/index/TestNorms.java > src/test/org/apache/lucene/index/TestParallelTermEnum.java > src/test/org/apache/lucene/index/TestSegmentTermEnum.java > src/test/org/apache/lucene/index/TestTerm.java > src/test/org/apache/lucene/index/TestTermVectorsReader.java > src/test/org/apache/lucene/search/TestRangeQuery.java > src/test/org/apache/lucene/search/TestTermScorer.java > src/test/org/apache/lucene/store/TestBufferedIndexInput.java > src/test/org/apache/lucene/store/TestWindowsMMap.java > src/test/org/apache/lucene/store/_TestHelper.java > src/test/org/apache/lucene/util/_TestUtil.java > contrib/benchmark/src/java/org/apache/lucene/benchmark/byTask/feeds/SimpleSloppyPhraseQueryMaker.java > contrib/gdata-server/src/core/src/java/org/apache/lucene/gdata/server/FeedNotFoundException.java > contrib/gdata-server/src/core/src/java/org/apache/lucene/gdata/server/registry/ComponentType.java > contrib/gdata-server/src/core/src/java/org/apache/lucene/gdata/server/registry/RegistryException.java > contrib/gdata-server/src/core/src/java/org/apache/lucene/gdata/storage/lucenestorage/StorageAccountWrapper.java > contrib/gdata-server/src/core/src/test/org/apache/lucene/gdata/storage/lucenestorage/TestModifiedEntryFilter.java > contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/AtomUriElementTest.java > contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMEntryImplTest.java > contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMFeedImplTest.java > contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMGenereatorImplTest.java > contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMSourceImplTest.java > contrib/highlighter/src/java/org/apache/lucene/search/highlight/TokenSources.java > contrib/javascript/queryConstructor/luceneQueryConstructor.js > contrib/javascript/queryEscaper/luceneQueryEscaper.js > contrib/javascript/queryValidator/luceneQueryValidator.js > contrib/queries/src/java/org/apache/lucene/search/BooleanFilter.java > contrib/queries/src/java/org/apache/lucene/search/BoostingQuery.java > contrib/queries/src/java/org/apache/lucene/search/FilterClause.java > contrib/queries/src/java/org/apache/lucene/search/FuzzyLikeThisQuery.java > contrib/queries/src/java/org/apache/lucene/search/TermsFilter.java > contrib/queries/src/java/org/apache/lucene/search/similar/MoreLikeThisQuery.java > contrib/queries/src/test/org/apache/lucene/search/BooleanFilterTest.java > contrib/regex/src/test/org/apache/lucene/search/regex/TestSpanRegexQuery.java > contrib/snowball/src/java/net/sf/snowball/Among.java > contrib/snowball/src/java/net/sf/snowball/SnowballProgram.java > contrib/snowball/src/java/net/sf/snowball/TestApp.java > contrib/spellchecker/src/test/org/apache/lucene/search/spell/TestSpellChecker.java > contrib/surround/src/test/org/apache/lucene/queryParser/surround/query/BooleanQueryTst.java > contrib/surround/src/test/org/apache/lucene/queryParser/surround/query/ExceptionQueryTst.java > contrib/surround/src/test/org/apache/lucene/queryParser/surround/query/SingleFieldTestDb.java > contrib/surround/src/test/org/apache/lucene/queryParser/surround/query/Test01Exceptions.java > contrib/surround/src/test/org/apache/lucene/queryParser/surround/query/Test02Boolean.java > contrib/surround/src/test/org/apache/lucen
[jira] Commented: (LUCENE-523) FSDirectory.openFile(String) causes ClassCastException
[ https://issues.apache.org/jira/browse/LUCENE-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495174 ] Jukka Zitting commented on LUCENE-523: -- We worked around the issue in Jackrabbit by using the new openInput method. I guess the underlying issue (FSDirectory.openFile throws an exception) is still there in Lucene, but I'm not sure if people are actually using that method. > FSDirectory.openFile(String) causes ClassCastException > -- > > Key: LUCENE-523 > URL: https://issues.apache.org/jira/browse/LUCENE-523 > Project: Lucene - Java > Issue Type: Bug > Components: Store >Affects Versions: 1.9, 2.0.0 > Environment: Lucene 1.9.1 >Reporter: Eric Isakson > > When you call FSDirectory.openFile(String) you get a ClassCastException since > FSIndexInput is not an org.apache.lucene.store.InputStream > The workaround is to reimplement using openInput(String). I personally don't > need this to be fixed but wanted to document it here in case anyone else runs > into this for any reason. > The reason I'm calling this is that I have a requirement on my project to > create read only indexes and name the index segments consistently from one > build to the next. So, after creating and optimizing the index, I rename the > files and rewrite the segments file. It would be nice if I had an API that > would allow me to say "I only want one segment and I want its name to be > 'foo'". For instance IndexWriter.optimize(String segmentName) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (LUCENE-734) Upload Lucene 2.0 artifacts in the Maven 1 repository
[ http://issues.apache.org/jira/browse/LUCENE-734?page=comments#action_12459126 ] Jukka Zitting commented on LUCENE-734: -- Digging deeper I found that the artifacts are actually located in the Maven 1 repository thanks to some URL rewrite magic, i.e. http://repo1.maven.org/maven/org.apache.lucene/jars/lucene-core-2.0.0.jar exists even though http://repo1.maven.org/maven/org.apache.lucene/jars/ returns a 404 error. So from my perspective it's OK to resolve this issue as Invalid. > FYI: anyone can edit the wiki if you create an account and login. Yes, thanks. I probably had the page locally cached since I still got the "immutable" message on the page after creating an account and logging in. Now it shows up as editable, I'll update the instructions. > Upload Lucene 2.0 artifacts in the Maven 1 repository > - > > Key: LUCENE-734 > URL: http://issues.apache.org/jira/browse/LUCENE-734 > Project: Lucene - Java > Issue Type: Task > Components: Other >Reporter: Jukka Zitting >Priority: Minor > > The Lucene 2.0 artifacts can be found in the Maven 2 repository, but not in > the Maven 1 repository. There are still projects using Maven 1 who might be > interested in upgrading to Lucene 2, so having the artifacts also in the > Maven 1 repository would be very helpful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (LUCENE-734) Upload Lucene 2.0 artifacts in the Maven 1 repository
[ http://issues.apache.org/jira/browse/LUCENE-734?page=comments#action_12454774 ] Jukka Zitting commented on LUCENE-734: -- The ReleaseTodo page is immutable so I can't modify it directly. At least the Maven sync directory information is outdated, the new official path (although I think the previous one is still symlinked) is /www/people.apache.org/repo/m2-ibiblio-rsync-repository. You are right in that the artifacts in the Maven 2 repository above should (AFAIK) get automatically copied also to the Maven 1 repository. At least it works the other way. I'll check that and report back. > Upload Lucene 2.0 artifacts in the Maven 1 repository > - > > Key: LUCENE-734 > URL: http://issues.apache.org/jira/browse/LUCENE-734 > Project: Lucene - Java > Issue Type: Task > Components: Other >Reporter: Jukka Zitting >Priority: Minor > > The Lucene 2.0 artifacts can be found in the Maven 2 repository, but not in > the Maven 1 repository. There are still projects using Maven 1 who might be > interested in upgrading to Lucene 2, so having the artifacts also in the > Maven 1 repository would be very helpful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (LUCENE-734) Upload Lucene 2.0 artifacts in the Maven 1 repository
Upload Lucene 2.0 artifacts in the Maven 1 repository - Key: LUCENE-734 URL: http://issues.apache.org/jira/browse/LUCENE-734 Project: Lucene - Java Issue Type: Task Components: Other Reporter: Jukka Zitting Priority: Minor The Lucene 2.0 artifacts can be found in the Maven 2 repository, but not in the Maven 1 repository. There are still projects using Maven 1 who might be interested in upgrading to Lucene 2, so having the artifacts also in the Maven 1 repository would be very helpful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (LUCENE-619) Lucene 1.9.1 and 2.0.0 Maven 2 packages are incorrectly deployed
[ http://issues.apache.org/jira/browse/LUCENE-619?page=comments#action_12432390 ] Jukka Zitting commented on LUCENE-619: -- The jars seem to be in place now. > Lucene 1.9.1 and 2.0.0 Maven 2 packages are incorrectly deployed > > > Key: LUCENE-619 > URL: http://issues.apache.org/jira/browse/LUCENE-619 > Project: Lucene - Java > Issue Type: Bug >Affects Versions: 1.9, 2.0.0 > Environment: > http://www.ibiblio.org/maven2/org/apache/lucene/lucene-core/ >Reporter: Jordan Christensen > > The lucene JARs at the URL listed in the Environment field only contain the > maven 2 POMs, and not the actual compiled classes. The correct JARs need to > be uploaded so that Lucene 1.9.1. and 2.0 can work in Maven 2. > This was listed as fixed in http://issues.apache.org/jira/browse/LUCENE-551, > but was not properly done. The JARs in the Apache Maven repo are incorrect as > well. > (http://www.apache.org/dist/maven-repository/org/apache/lucene/lucene-core/) > This issue was raised and confirmed on the mailing list as well: > http://www.gossamer-threads.com/lists/lucene/java-user/37169 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (LUCENE-658) upload major releases to ibiblio
[ http://issues.apache.org/jira/browse/LUCENE-658?page=comments#action_12432389 ] Jukka Zitting commented on LUCENE-658: -- This seems to be a duplicate of LUCENE-551. The releases are available at: http://www.ibiblio.org/maven2/org/apache/lucene/lucene-core/ > upload major releases to ibiblio > > > Key: LUCENE-658 > URL: http://issues.apache.org/jira/browse/LUCENE-658 > Project: Lucene - Java > Issue Type: Task > Components: Other >Affects Versions: 1.9, 2.0.0 >Reporter: Ryan Sonnek > > i'm a current user of maven and the latest 1.9 and 2.0 releases are not > available on ibiblio. > http://www.ibiblio.org/maven2/lucene/lucene/ > Could someone upload the latest versions so that use maven-heads can access > the new features? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (LUCENE-523) FSDirectory.openFile(String) causes ClassCastException
[ http://issues.apache.org/jira/browse/LUCENE-523?page=comments#action_12371018 ] Jukka Zitting commented on LUCENE-523: -- The related Jackrabbit issue is http://issues.apache.org/jira/browse/JCR-352 > FSDirectory.openFile(String) causes ClassCastException > -- > > Key: LUCENE-523 > URL: http://issues.apache.org/jira/browse/LUCENE-523 > Project: Lucene - Java > Type: Bug > Components: Store > Versions: 1.9, 2.0 > Environment: Lucene 1.9.1 > Reporter: Eric Isakson > > When you call FSDirectory.openFile(String) you get a ClassCastException since > FSIndexInput is not an org.apache.lucene.store.InputStream > The workaround is to reimplement using openInput(String). I personally don't > need this to be fixed but wanted to document it here in case anyone else runs > into this for any reason. > The reason I'm calling this is that I have a requirement on my project to > create read only indexes and name the index segments consistently from one > build to the next. So, after creating and optimizing the index, I rename the > files and rewrite the segments file. It would be nice if I had an API that > would allow me to say "I only want one segment and I want its name to be > 'foo'". For instance IndexWriter.optimize(String segmentName) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
