Solr nightly build failure
init-forrest-entities: [mkdir] Created dir: /tmp/apache-solr-nightly/build checkJunitPresence: compile-common: [mkdir] Created dir: /tmp/apache-solr-nightly/build/common [javac] Compiling 26 source files to /tmp/apache-solr-nightly/build/common [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. compile: [mkdir] Created dir: /tmp/apache-solr-nightly/build/core [javac] Compiling 213 source files to /tmp/apache-solr-nightly/build/core [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. compile-solrj-core: [mkdir] Created dir: /tmp/apache-solr-nightly/build/client/solrj [javac] Compiling 21 source files to /tmp/apache-solr-nightly/build/client/solrj [javac] Note: /tmp/apache-solr-nightly/client/java/solrj/src/org/apache/solr/client/solrj/impl/CommonsHttpSolrServer.java uses or overrides a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. compile-solrj: [javac] Compiling 2 source files to /tmp/apache-solr-nightly/build/client/solrj [javac] Note: /tmp/apache-solr-nightly/client/java/solrj/src/org/apache/solr/client/solrj/embedded/JettySolrRunner.java uses or overrides a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. compileTests: [mkdir] Created dir: /tmp/apache-solr-nightly/build/tests [javac] Compiling 58 source files to /tmp/apache-solr-nightly/build/tests [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. junit: [mkdir] Created dir: /tmp/apache-solr-nightly/build/test-results [junit] Running org.apache.solr.BasicFunctionalityTest [junit] Tests run: 25, Failures: 0, Errors: 0, Time elapsed: 28.253 sec [junit] Running org.apache.solr.ConvertedLegacyTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 7.263 sec [junit] Running org.apache.solr.DisMaxRequestHandlerTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 6.321 sec [junit] Running org.apache.solr.EchoParamsTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.397 sec [junit] Running org.apache.solr.OutputWriterTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3.323 sec [junit] Running org.apache.solr.SampleTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.512 sec [junit] Running org.apache.solr.analysis.TestBufferedTokenStream [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.05 sec [junit] Running org.apache.solr.analysis.TestCapitalizationFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.133 sec [junit] Running org.apache.solr.analysis.TestHyphenatedWordsFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.045 sec [junit] Running org.apache.solr.analysis.TestKeepWordFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.054 sec [junit] Running org.apache.solr.analysis.TestPatternReplaceFilter [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.045 sec [junit] Running org.apache.solr.analysis.TestPatternTokenizerFactory [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.059 sec [junit] Running org.apache.solr.analysis.TestPhoneticFilter [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.076 sec [junit] Running org.apache.solr.analysis.TestRemoveDuplicatesTokenFilter [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.047 sec [junit] Running org.apache.solr.analysis.TestSynonymFilter [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.21 sec [junit] Running org.apache.solr.analysis.TestTrimFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.047 sec [junit] Running org.apache.solr.analysis.TestWordDelimiterFilter [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 5.521 sec [junit] Running org.apache.solr.common.SolrDocumentTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.053 sec [junit] Running org.apache.solr.common.params.SolrParamTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.064 sec [junit] Running org.apache.solr.common.util.ContentStreamTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 4.912 sec [junit] Running org.apache.solr.common.util.IteratorChainTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.044 sec [junit] Running org.apache.solr.common.util.TestXMLEscaping
[jira] Commented: (SOLR-196) A PHP response writer for Solr
[ https://issues.apache.org/jira/browse/SOLR-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517552 ] Yonik Seeley commented on SOLR-196: --- Thanks Pieter, Regarding the content-type, I found it more useful to be able to actually see the result in a browser. Is there a content-type we can use for JSON that can achieve both goals for firefox and IE at least? A PHP response writer for Solr -- Key: SOLR-196 URL: https://issues.apache.org/jira/browse/SOLR-196 Project: Solr Issue Type: New Feature Components: clients - php, search Reporter: Paul Borgermans Attachments: SOLR-192-php-responsewriter.patch, SOLR-196-PHPResponseWriter.patch It would be useful to have a PHP response writer that returns an array to be eval-ed directly. This is especially true for PHP4.x installs, where there is no built in support for JSON. This issue attempts to address this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-280) slightly more efficient SolrDocument implementation
[ https://issues.apache.org/jira/browse/SOLR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley resolved SOLR-280. Resolution: Fixed resolving an old issue slightly more efficient SolrDocument implementation --- Key: SOLR-280 URL: https://issues.apache.org/jira/browse/SOLR-280 Project: Solr Issue Type: Improvement Reporter: Ryan McKinley Assignee: Ryan McKinley Priority: Minor Attachments: SOLR-280-SolrDocument2-API-Compatibility.patch, SOLR-280-SolrDocument2.patch, SOLR-280-SolrDocument2.patch Following discussion in SOLR-272 This implementation stores fields as a MapString,Object rather then a MapString,CollectionObject. The API changes slightly in that: getFieldValue( name ) returns a Collection if there are more then one fields and a Object if there is only one. getFirstValue( name ) returns a single value for the field. This is intended to make things easier for client applications. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-225) Allow pluggable Highlighting classes -- Formatters and Fragmenters
[ https://issues.apache.org/jira/browse/SOLR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley resolved SOLR-225. Resolution: Fixed added a while ago Allow pluggable Highlighting classes -- Formatters and Fragmenters -- Key: SOLR-225 URL: https://issues.apache.org/jira/browse/SOLR-225 Project: Solr Issue Type: Improvement Reporter: Brian Whitman Assignee: Ryan McKinley Attachments: SOLR-225+260-HighlightPlugins.patch, SOLR-225+260-HighlightPlugins.patch, SOLR-225-HighlightingConfig.patch, SOLR-225-HighlightingConfig.patch, SOLR-225-HighlightingConfig.patch, SOLR-225-HighlightingConfig.patch, SOLR-225-HighlightingConfig.patch Highlighting should support a pluggable architecture similar to what is seen with RequestHandlers, Fields, FieldTypes, etc ' For more background: http://www.nabble.com/Custom-fragmenter-tf3681588.html#a10289335 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-248) Capitalization Filter Factory
[ https://issues.apache.org/jira/browse/SOLR-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley resolved SOLR-248. Resolution: Fixed added a while ago Capitalization Filter Factory - Key: SOLR-248 URL: https://issues.apache.org/jira/browse/SOLR-248 Project: Solr Issue Type: New Feature Reporter: Ryan McKinley Assignee: Ryan McKinley Priority: Minor Attachments: SOLR-248-CapitalizationFilter.patch, SOLR-248-CapitalizationFilter.patch, SOLR-248-CapitalizationFilter.patch For tokens that are used in faceting, it is nice to have standard capitalization. I want Aerial views and Aerial Views to both be: Aerial Views -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Solr nightly build failure
[junit] Running org.apache.solr.update.AutoCommitTest [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 20.424 sec [junit] Test org.apache.solr.update.AutoCommitTest FAILED This is how long it takes to run on my (medium-loaded) system: junit: [junit] Running org.apache.solr.update.AutoCommitTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.514 sec Yonik could you see whether it is maxDocs or maxTime that is failing? Thanks, -Mike
[jira] Commented: (SOLR-326) cleanup eclipse warnings
[ https://issues.apache.org/jira/browse/SOLR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517660 ] Otis Gospodnetic commented on SOLR-326: --- Does Eclipse take into account class references in javadocs? I *think* those are needed as imports in order for javadocs not to issue warnings. cleanup eclipse warnings Key: SOLR-326 URL: https://issues.apache.org/jira/browse/SOLR-326 Project: Solr Issue Type: Improvement Reporter: Paul Sundling Priority: Minor Attachments: remove_unused_imports_patch.txt On default settings, Eclipse had 628 warnings. This patch removes 119 of those warnings related to unused imports. These are the safest warnings to fix and shouldn't require any testing other than confirming building still works. The general idea of removing warnings is both cleaner code, but also making it easier for interesting warnings to get hidden by uninteresting warnings. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-326) cleanup eclipse warnings
[ https://issues.apache.org/jira/browse/SOLR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517674 ] Paul Sundling commented on SOLR-326: I just ran ant clean javadoc and it had 14 errors (not bad for a code base of this size!). Although my patch touches a lot of classes, none of them were classes I touched (judging from the '' I see in subversive eclipse plugin for files that were modified. I think Eclipse is smart enough and I've seen it add imports when I add annotations. I don't use @see in javadocs that often. Let me know if you see different behavior. I reverted my changes locally and still had the same 14 javadoc errors. So I'm pretty confident that I didn't introduce errors in the patch. cleanup eclipse warnings Key: SOLR-326 URL: https://issues.apache.org/jira/browse/SOLR-326 Project: Solr Issue Type: Improvement Reporter: Paul Sundling Priority: Minor Attachments: remove_unused_imports_patch.txt On default settings, Eclipse had 628 warnings. This patch removes 119 of those warnings related to unused imports. These are the safest warnings to fix and shouldn't require any testing other than confirming building still works. The general idea of removing warnings is both cleaner code, but also making it easier for interesting warnings to get hidden by uninteresting warnings. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-327) shell scripts failed to run on Solaris 8 (and probably other non recent UNIX)
shell scripts failed to run on Solaris 8 (and probably other non recent UNIX) - Key: SOLR-327 URL: https://issues.apache.org/jira/browse/SOLR-327 Project: Solr Issue Type: Bug Reporter: Paul Sundling Priority: Minor There are several places where commands used are incompatible with older UNIX versions, even though these capabilities are present. There are ways to rewrite the shell scripts to be compatible with these older versions. The first example is the use of pgrep. Older machines will have grep, egrep and fgrep, but NOT pgrep. I've been doing UNIX for well over a decade and never heard of pgrep, although it is installed on my home server apparently. :) There are also enhancements like the use of 'cp -l'. This could be accomplished with the 'ln' command instead on older UNIX versions. Since it's also used recursively in snapshooter, which 'ln' doesn't support, it makes the command more complex. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
