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 215 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: 18.431 sec [junit] Running org.apache.solr.ConvertedLegacyTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 6.572 sec [junit] Running org.apache.solr.DisMaxRequestHandlerTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3.773 sec [junit] Running org.apache.solr.EchoParamsTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.434 sec [junit] Running org.apache.solr.OutputWriterTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.651 sec [junit] Running org.apache.solr.SampleTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.849 sec [junit] Running org.apache.solr.analysis.TestBufferedTokenStream [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.044 sec [junit] Running org.apache.solr.analysis.TestCapitalizationFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.048 sec [junit] Running org.apache.solr.analysis.TestHyphenatedWordsFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.048 sec [junit] Running org.apache.solr.analysis.TestKeepWordFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.046 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.056 sec [junit] Running org.apache.solr.analysis.TestPhoneticFilter [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.061 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.069 sec [junit] Running org.apache.solr.analysis.TestTrimFilter [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.044 sec [junit] Running org.apache.solr.analysis.TestWordDelimiterFilter [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 4.919 sec [junit] Running org.apache.solr.common.SolrDocumentTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.05 sec [junit] Running org.apache.solr.common.params.SolrParamTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.054 sec [junit] Running org.apache.solr.common.util.ContentStreamTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.403 sec [junit] Running org.apache.solr.common.util.IteratorChainTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.042 sec [junit] Running org.apache.solr.common.util.TestXMLEscaping
PHP Solr Client source
The company I work for recently started using Solr for some of our
search functionality. After downloading the files for integrating
with PHP that the Wiki links to I saw that it wasn't usable for our
purposes. So, as part of the project, I developed a PHP Solr Client.
Coming back to the mailing list I see that there was recent talk
about developing a new PHP client, but as of yet I haven't seen it
posted - so I hope I'm not stepping on any toes. I received
permission from my company to release the code to the community under
the new BSD license. The coding style is approximately inline with
the Zend Framework's standards (and somewhat PEAR's) and I feel it's
well documented.
Client Requirements:
- PHP 5 = 5.2.0 (we developed on 5.2.1) that has the json_decode
function (available by default as of 5.2) and the XmlReader class
(enabled by default as of 5.1)
- allow_url_fopen php.ini setting must be enabled (defaults to
enabled)
We'd love to have the community help us maintain this as Solr
evolves. Let us know what you think. Thanks.
- Donovan Jimenez
For those interested:
The starting point is the Solr_Service class. From this class you
have access to all the major functionality of the Solr HTTP service
(add, delete by id, delete by query, commit, optimize and search).
Below I've include a sample of the client's API for searching:
?php
require_once('Solr/Service.php');
$start = microtime(true);
$solr = new Solr_Service(); //Or explicitly new Solr_Service
('localhost', 8180, '/solr');
try
{
$response = $solr-search('solr', 0, 10,
array(/* you can include other parameters here */));
echo 'search returned with status = ', $response-
responseHeader-status,
' and took ', microtime(true) - $start, ' seconds',
\n;
//here's how you would access results
//Notice that I've mapped the values by name into a tree of
stdClass objects
//and arrays (actually most of this is done by json_decode
if the response is
//in json format - done by an XmlReader loop if its XML)
if ($response-response-numFound 0)
{
$doc_number = $response-response-start;
foreach ($response-response-docs as $doc)
{
$doc_number++;
echo $doc_number, ': ', $doc-text, \n;
}
}
//for the purposes of seeing the available structure of the
response
//NOTE: Solr_Response::_parsedData is lazy loaded, so a
print_r on the response before
//any values are accessed may result in different behavior
(in case
//anyone has some troubles debugging)
//print_r($response);
}
catch (Exception $e)
{
echo $e-getMessage(), \n;
}
?
[jira] Commented: (SOLR-281) Search Components (plugins)
[ https://issues.apache.org/jira/browse/SOLR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520434 ] Pieter Berkel commented on SOLR-281: I just tried this patch on svn trunk (r566899) and got the following failures: $ patch -p0 ../SOLR-281-SearchComponents.patch ... patching file src/java/org/apache/solr/handler/StandardRequestHandler.java Hunk #1 succeeded at 17 with fuzz 1. Hunk #2 FAILED at 45. 1 out of 2 hunks FAILED -- saving rejects to file src/java/org/apache/solr/handler/StandardRequestHandler.java.rej ... patching file src/java/org/apache/solr/handler/DisMaxRequestHandler.java Hunk #1 FAILED at 17. 1 out of 1 hunk FAILED -- saving rejects to file src/java/org/apache/solr/handler/DisMaxRequestHandler.java.rej I suspect it is the changes made by SOLR-326 that is causing the these problems, would it be possible for you to create a new patch? thanks, Piete Search Components (plugins) --- Key: SOLR-281 URL: https://issues.apache.org/jira/browse/SOLR-281 Project: Solr Issue Type: New Feature Reporter: Ryan McKinley Attachments: SOLR-281-SearchComponents.patch, SOLR-281-SearchComponents.patch, SOLR-281-SearchComponents.patch A request handler with pluggable search components for things like: - standard - dismax - more-like-this - highlighting - field collapsing For more discussion, see: http://www.nabble.com/search-components-%28plugins%29-tf3898040.html#a11050274 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: PHP Solr Client source
Hi Donovan,
This sounds very promising, I've also recently been working on a php solr
client library for use within my organization but the code is not well
documented nor licensed appropriately just yet. You may note that
eval()-able and serialized php response writers were recently added to svn
trunk (see http://issues.apache.org/jira/browse/SOLR-196 ) so it may be more
efficient to use these rather than converting XML / JSON formatted data.
In terms of licensing, I'm not sure if the new BSD license is compatible
with the Apache 2.0 license (see:
http://www.apache.org/licenses/LICENSE-2.0) that Solr is released
under, this would only be an issue if your php
client was to be included in the Solr distribution (which would be useful
but not manditory).
I'd be interested to take a look at your client library code, are you
planning to release it soon?
regards,
Piete
On 17/08/07, Donovan Jimenez [EMAIL PROTECTED] wrote:
The company I work for recently started using Solr for some of our
search functionality. After downloading the files for integrating
with PHP that the Wiki links to I saw that it wasn't usable for our
purposes. So, as part of the project, I developed a PHP Solr Client.
Coming back to the mailing list I see that there was recent talk
about developing a new PHP client, but as of yet I haven't seen it
posted - so I hope I'm not stepping on any toes. I received
permission from my company to release the code to the community under
the new BSD license. The coding style is approximately inline with
the Zend Framework's standards (and somewhat PEAR's) and I feel it's
well documented.
Client Requirements:
- PHP 5 = 5.2.0 (we developed on 5.2.1) that has the json_decode
function (available by default as of 5.2) and the XmlReader class
(enabled by default as of 5.1)
- allow_url_fopen php.ini setting must be enabled (defaults to
enabled)
We'd love to have the community help us maintain this as Solr
evolves. Let us know what you think. Thanks.
- Donovan Jimenez
For those interested:
The starting point is the Solr_Service class. From this class you
have access to all the major functionality of the Solr HTTP service
(add, delete by id, delete by query, commit, optimize and search).
Below I've include a sample of the client's API for searching:
?php
require_once('Solr/Service.php');
$start = microtime(true);
$solr = new Solr_Service(); //Or explicitly new Solr_Service
('localhost', 8180, '/solr');
try
{
$response = $solr-search('solr', 0, 10,
array(/* you can include other parameters here */));
echo 'search returned with status = ', $response-
responseHeader-status,
' and took ', microtime(true) - $start, ' seconds',
\n;
//here's how you would access results
//Notice that I've mapped the values by name into a tree of
stdClass objects
//and arrays (actually most of this is done by json_decode
if the response is
//in json format - done by an XmlReader loop if its XML)
if ($response-response-numFound 0)
{
$doc_number = $response-response-start;
foreach ($response-response-docs as $doc)
{
$doc_number++;
echo $doc_number, ': ', $doc-text, \n;
}
}
//for the purposes of seeing the available structure of the
response
//NOTE: Solr_Response::_parsedData is lazy loaded, so a
print_r on the response before
//any values are accessed may result in different behavior
(in case
//anyone has some troubles debugging)
//print_r($response);
}
catch (Exception $e)
{
echo $e-getMessage(), \n;
}
?
