Solr nightly build failure
checkJunitPresence: compile: [mkdir] Created dir: /tmp/apache-solr-nightly/build [javac] Compiling 172 source files to /tmp/apache-solr-nightly/build [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. compileTests: [mkdir] Created dir: /tmp/apache-solr-nightly/build/tests [javac] Compiling 30 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: 23, Failures: 0, Errors: 0, Time elapsed: 28.485 sec [junit] Running org.apache.solr.ConvertedLegacyTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 15.089 sec [junit] Running org.apache.solr.DisMaxRequestHandlerTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 10.28 sec [junit] Running org.apache.solr.EchoParamsTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.608 sec [junit] Running org.apache.solr.HighlighterTest [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 19.116 sec [junit] Running org.apache.solr.IndexInfoRequestHandlerTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.802 sec [junit] Running org.apache.solr.OutputWriterTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 4.548 sec [junit] Running org.apache.solr.SampleTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.09 sec [junit] Running org.apache.solr.analysis.TestBufferedTokenStream [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.079 sec [junit] Running org.apache.solr.analysis.TestHyphenatedWordsFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.057 sec [junit] Running org.apache.solr.analysis.TestPatternReplaceFilter [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.073 sec [junit] Running org.apache.solr.analysis.TestRemoveDuplicatesTokenFilter [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.083 sec [junit] Running org.apache.solr.analysis.TestSynonymFilter [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.103 sec [junit] Running org.apache.solr.analysis.TestTrimFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.072 sec [junit] Running org.apache.solr.analysis.TestWordDelimiterFilter [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.388 sec [junit] Running org.apache.solr.core.TestBadConfig [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.243 sec [junit] Running org.apache.solr.core.TestConfig [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.554 sec [junit] Running org.apache.solr.search.TestDocSet [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.668 sec [junit] Running org.apache.solr.search.TestQueryUtils [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 10.025 sec [junit] Running org.apache.solr.servlet.SolrRequestParserTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 7.15 sec [junit] Running org.apache.solr.update.AutoCommitTest [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 7.395 sec [junit] Test org.apache.solr.update.AutoCommitTest FAILED [junit] Running org.apache.solr.update.DirectUpdateHandlerTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.86 sec [junit] Running org.apache.solr.util.DateMathParserTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.175 sec [junit] Running org.apache.solr.util.IteratorChainTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.063 sec [junit] Running org.apache.solr.util.SolrPluginUtilsTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 10.948 sec [junit] Running org.apache.solr.util.TestOpenBitSet [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.243 sec [junit] Running org.apache.solr.util.TestUtils [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.055 sec [junit] Running org.apache.solr.util.TestXMLEscaping [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.056 sec BUILD FAILED /tmp/apache-solr-nightly/build.xml:298: Tests failed! Total time: 2 minutes 55 seconds
[jira] Commented: (SOLR-183) add getRequiredParameter() to SolrParams
[
https://issues.apache.org/jira/browse/SOLR-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482686
]
J.J. Larrea commented on SOLR-183:
--
Thanks for clarifying the semantics and the implementation, Ryan.
It's fine by me to remove the strictField logic from getFieldParam; as I
said, I wasn't sure there would be any cases where a developer considered
defining a non-field-limited value (facet.limit) an insufficient means to
fulfill definition of a field-specific value (f.xxx.facet.limit). Should such
a case ever arise, they could subclass RequiredSolrParams to override
getFieldParam and accomplish that themself.
add getRequiredParameter() to SolrParams
Key: SOLR-183
URL: https://issues.apache.org/jira/browse/SOLR-183
Project: Solr
Issue Type: Wish
Reporter: Ryan McKinley
Priority: Trivial
Attachments: RequiredSolrParams.java, SOLR-183-required-param.patch,
SOLR-183-required-param.patch, SOLR-183-required-param.patch,
SOLR-183-required-param.patch, SOLR-183-required-param.patch
I find myself including this with every patch, so i'll just separate it out.
This simply adds a utilty function to SolrParams that throws a 400 if the
parameter is missing:
/** returns the value of the param, or throws a 400 exception if missing */
public String getRequiredParameter(String param) throws SolrException {
String val = get(param);
if( val == null ) {
throw new SolrException( 400, Missing parameter: +param );
}
return val;
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-194) SimplePostTool incorrectly uses the current JVM encoding to read files
SimplePostTool incorrectly uses the current JVM encoding to read files -- Key: SOLR-194 URL: https://issues.apache.org/jira/browse/SOLR-194 Project: Solr Issue Type: Bug Components: clients - java Reporter: Bertrand Delacretaz Priority: Minor Using java -Dfile.encoding=iso-8859-1 -jar post.jar http://localhost:8983/solr/update utf8-example.xml posts incorrect data, apparently utf8-example.xml is read using the JVM's encoding. As a workaround before we fix this, use java -Dfile.encoding=UTF-8 -jar post.jar http://localhost:8983/solr/update utf8-example.xml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-194) SimplePostTool uses hardcoded UTF-8 encoding to read files
[ https://issues.apache.org/jira/browse/SOLR-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SOLR-194: - Summary: SimplePostTool uses hardcoded UTF-8 encoding to read files (was: SimplePostTool incorrectly uses the current JVM encoding to read files) SimplePostTool uses hardcoded UTF-8 encoding to read files -- Key: SOLR-194 URL: https://issues.apache.org/jira/browse/SOLR-194 Project: Solr Issue Type: Bug Components: clients - java Reporter: Bertrand Delacretaz Priority: Minor Using java -Dfile.encoding=iso-8859-1 -jar post.jar http://localhost:8983/solr/update utf8-example.xml posts incorrect data, apparently utf8-example.xml is read using the JVM's encoding. As a workaround before we fix this, use java -Dfile.encoding=UTF-8 -jar post.jar http://localhost:8983/solr/update utf8-example.xml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-194) SimplePostTool uses hardcoded UTF-8 encoding to read files
[ https://issues.apache.org/jira/browse/SOLR-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SOLR-194: - Attachment: post.jar Includes the fix of revision 520817 SimplePostTool uses hardcoded UTF-8 encoding to read files -- Key: SOLR-194 URL: https://issues.apache.org/jira/browse/SOLR-194 Project: Solr Issue Type: Bug Components: clients - java Reporter: Bertrand Delacretaz Priority: Minor Attachments: post.jar Using java -Dfile.encoding=iso-8859-1 -jar post.jar http://localhost:8983/solr/update utf8-example.xml posts incorrect data, apparently utf8-example.xml is read using the JVM's encoding. As a workaround before we fix this, use java -Dfile.encoding=UTF-8 -jar post.jar http://localhost:8983/solr/update utf8-example.xml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[ApacheCon] Early Bird registration ends Tuesday March 27th
Hi everybody, Please note that the Early Bird registration for the ApacheCon Europe 2007 (May 1-4, Amsterdam) ends soon, see below for the official announcement. See http://www.eu.apachecon.com/ for more details and for the program. Hope to see you there! -Bertrand --- Early Bird Registration for ApacheCon Europe 2007 Ends Tuesday 27 March World-Recognized Technologists, Vendors, Thought-Leaders, and Users Convene in Amsterdam to Experience the Future of Open Source Development FOREST HILL, MD -- (MARKET WIRE) -- March 21, 2007 -- ApacheCon Europe 2007, the official conference, trainings, and expo of the Apache Software Foundation (ASF), today announced the deadline for Early Bird registration ends on Tuesday, 27 March 2007. With engaging plenary and keynote addresses, technical presentations, informal networking, peer discussions, Birds-of-a-Feather sessions, and entertaining social events, ApacheCon delves into the highly lauded community that develops and shepherds industry-leading Open Source projects, including Apache HTTP Server -- the world's most popular Web server software for more than a decade. ApacheCon Europe takes place 1-4 May 2007 at the Mövenpick Hotel in Amsterdam, The Netherlands. Special Registration-Plus-Hotel Conference Package offers savings up to US$238; Conference passes range from US$450 - US$1,700 with an average savings of US$150 with Early Bird pricing. Trainings are US$350 for half-day sessions, and US$550 for full-day courses. Register today at http://www.eu.apachecon.com/. With more than 100 sessions on groundbreaking technologies and emerging industry trends, conference participants meet, mingle, and exchange ideas with like-minded peers in a relaxed, community-focused environment. Highlights include: Abstraction and extraction: in praise of: Keynote addresses from Steven Pemberton, Web Usability Expert at CWI and Chair, W3C XHTML and XForms Working Groups. Open Source: It's a license, not a business model or a development model: Keynote address by Dr. Margo Seltzer, Herchel Smith Professor of Computer Science, Harvard University Division of Applied Sciences. Full-and Half-Day Training Sessions taught by industry experts, offering hands-on instruction on Apache Projects Axis2, ApacheDS, Jackrabbit, Jetspeed, HTTP Server, Lucene, Maven, MyFaces, emerging initiatives from the Apache Incubator, and widely-deployed standards such as SSL and XSLT. Popular Developer Presentations on flagship Apache and Open Source technologies, including Geronimo, Harmony, HTTP Server, Tomcat, AJAX, Cocoon, Databases, Derby, Eclipse, Jakarta, LDAP, Portlets, Roller, Security, SpamAssassin, and WebDAV, as well as a look into projects from the ASF Incubator and Labs at the new ApacheCon Fast Feather Track. Business Track featuring panel sessions, presentations, and case studies that address core Open Source business, marketing, standardization, community-building, and legal/licensing issues, as well as explore broader areas such as the Semantic Web, Web Services, Web 2.0, and mobile technologies. Sponsor Events and Expo gives attendees direct access to industry-leading organizations such as BlackHat, Covalent, Google (NASDAQ: GOOG), the Java Community Process, and Sun Microsystems (NASDAQ: SUNW) as well as first-looks at new technologies and products showcased by emerging players such as Hippo, Nexaweb, Ordina, and WSO2. Special Events include geeking, hacking, and relaxing in the Online Lounge, conference and sponsor receptions, out-of-the-box public speaking at the Lighting Talks, and more! Corporate Sponsorship, Exhibitor, and government participation opportunities are available; contact Delia Frees at [EMAIL PROTECTED] or on +1 707 765 0823 for more information. Event media partners include: Apress, CMS Channel, CMS Center, DevTownStation, DigiMedia, European Web Association, Free Software Magazine, Integration Developer News, Linux Magazine, LXer, Methods Tools, Open Enterprise Trends, Slashdot, Software Development Articles Directory, Software Development Tools Directory, Software Development News, and Webtech 2007. To become a Media Partner, contact Sally Khudairi on +1 617 921 8656 or [EMAIL PROTECTED]
[jira] Commented: (SOLR-131) tutorial update: faceting, highlighting, etc
[ https://issues.apache.org/jira/browse/SOLR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482951 ] Hoss Man commented on SOLR-131: --- FYI: the decision was made when post.jar was created that the tutorial on the site should refer to the current trunk, since the releases each contain their own snapshot of the tutorial at the moment of the release tutorial update: faceting, highlighting, etc Key: SOLR-131 URL: https://issues.apache.org/jira/browse/SOLR-131 Project: Solr Issue Type: Improvement Components: documentation Reporter: Yonik Seeley The tutorial hasn't really been changed since we entered the incubator. Highlighting and Faceting might be nice additions. Looking back, I wish I had chosen a different data set like books or movies (or a mix of both)... something that wouldn't get out of date as fast as electronics, and that more people could identify with. The biggest downside is examples in the Wiki refer to the current example docs. breaking into multiple pages, and a screenshot or two wouldn't be bad idea either. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
