[jira] Commented: (SOLR-73) schema.xml and solrconfig.xml use CNET-internal class names
[ http://issues.apache.org/jira/browse/SOLR-73?page=comments#action_12454164 ] Philip Jacob commented on SOLR-73: -- Fwiw, I agree with Walt and Bertrand here. Full class names are less ambiguous. schema.xml and solrconfig.xml use CNET-internal class names --- Key: SOLR-73 URL: http://issues.apache.org/jira/browse/SOLR-73 Project: Solr Issue Type: Bug Components: search Reporter: Walter Underwood The configuration files in the example directory still use the old CNET-internal class names, like solr.LRUCache instead of org.apache.solr.search.LRUCache. This is confusing to new users and should be fixed before the first release. -- 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
[jira] Updated: (SOLR-35) URL escaping problems in webapp
[ http://issues.apache.org/jira/browse/SOLR-35?page=all ] Philip Jacob updated SOLR-35: - Attachment: patch-utf-8-problems-webapp.patch URL escaping problems in webapp --- Key: SOLR-35 URL: http://issues.apache.org/jira/browse/SOLR-35 Project: Solr Issue Type: Bug Components: search Environment: Darwin berlin.local 8.7.1 Darwin Kernel Version 8.7.1: Wed Jun 7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386 i386 i386 Reporter: Philip Jacob Attachments: patch-utf-8-problems-webapp.patch, patch-utf-8-problems.patch Tricia Williams reported problems with Cyrillic charsets when trying to search using the admin application, specifically NPEs and bad results. This patch fixes the webapp by specifying a character encoding for each of the admin pages. I also discovered a second issue in StrUtils that wasn't encoding UTF-8 data properly, so I fixed that. I'm attaching 2 patches. -- 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
[jira] Commented: (SOLR-30) Java client code for performing searches against a Solr instance
[ http://issues.apache.org/jira/browse/SOLR-30?page=comments#action_12421469 ] Philip Jacob commented on SOLR-30: -- Thanks for the comments. Here are my thoughts: 1) Good point. One approach for doing this would be to what Commons Configuration does. I could add methods to Field to perform getValueAsInteger(), getValueAsBoolean(), etc. These are basically just convenient methods. The other approach would be to change Field.value to Object instead of String. And then it's up to the client code to figure out what Object is (presumably using instanceof). So while I agree with your idea, I'm not sure what people think the best way to do this is. 2) JDOM - agreed. I just did it this way because writing DOM code takes me five times longer :) But, yes, it should go. Commons HttpClient, on the other hand, has a *lot* of useful stuff like multhreaded connection management and connection persistence. Even in medium-volume situations, these optimizations will make a difference. The prospect of implementing a subset of the functionality in Commons HttpClient is not an enviable task. 3) Actually, that was a question I had. Are those fields always guaranteed to be there in Solr's response? If not, then they ought to able to contain null so that means they could be Integers. If Solr guarantees that these fields will always be in the response, then they definitely could be ints. Other thoughts? Java client code for performing searches against a Solr instance Key: SOLR-30 URL: http://issues.apache.org/jira/browse/SOLR-30 Project: Solr Issue Type: New Feature Components: search Reporter: Philip Jacob Priority: Minor Attachments: solrsearcher-client.zip Here are a few classes that connect to a Solr instance to perform searches. Results are returned in a Response object. The Response encapsulates a ListMapString,Field that gives you access to the key data in the results. This is the main part that I'm looking for comments on. There are 2 dependencies for this code: JDOM and Commons HttpClient. I'll remove the JDOM dependency in favor of regular DOM at some point, but I think that the HttpClient dependency is worthwhile here. There's a lot that can be exploited with HttpClient that isn't demonstrated in this class. The purpose here is mainly to get feedback on the API of SolrSearcher before I start optimizing anything. -- 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
[jira] Created: (SOLR-29) backup utility does not work on OS X
backup utility does not work on OS X Key: SOLR-29 URL: http://issues.apache.org/jira/browse/SOLR-29 Project: Solr Issue Type: Bug Environment: Darwin berlin.local 8.7.1 Darwin Kernel Version 8.7.1: Wed Jun 7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386 i386 i386 Reporter: Philip Jacob The 'cp' command on OS X doesn't support the -l option, so the backup script doesn't work. -- 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
[jira] Created: (SOLR-30) Java client code for performing searches against a Solr instance
Java client code for performing searches against a Solr instance Key: SOLR-30 URL: http://issues.apache.org/jira/browse/SOLR-30 Project: Solr Issue Type: New Feature Components: search Reporter: Philip Jacob Priority: Minor Here are a few classes that connect to a Solr instance to perform searches. Results are returned in a Response object. The Response encapsulates a ListMapString,Field that gives you access to the key data in the results. This is the main part that I'm looking for comments on. There are 2 dependencies for this code: JDOM and Commons HttpClient. I'll remove the JDOM dependency in favor of regular DOM at some point, but I think that the HttpClient dependency is worthwhile here. There's a lot that can be exploited with HttpClient that isn't demonstrated in this class. The purpose here is mainly to get feedback on the API of SolrSearcher before I start optimizing anything. -- 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
[jira] Updated: (SOLR-30) Java client code for performing searches against a Solr instance
[ http://issues.apache.org/jira/browse/SOLR-30?page=all ]
Philip Jacob updated SOLR-30:
-
Attachment: solrsearcher-client.zip
Attachment contains:
Length Date TimeName
804 07-16-06 00:37
solr-trunk/src/java/org/apache/solr/client/Field.java
1337 07-16-06 00:37
solr-trunk/src/java/org/apache/solr/client/Response.java
390 07-16-06 00:37
solr-trunk/src/java/org/apache/solr/client/SearchException.java
5873 07-16-06 00:37
solr-trunk/src/java/org/apache/solr/client/SolrSearcher.java
---
8404 4 files
Java client code for performing searches against a Solr instance
Key: SOLR-30
URL: http://issues.apache.org/jira/browse/SOLR-30
Project: Solr
Issue Type: New Feature
Components: search
Reporter: Philip Jacob
Priority: Minor
Attachments: solrsearcher-client.zip
Here are a few classes that connect to a Solr instance to perform searches.
Results are returned in a Response object. The Response encapsulates a
ListMapString,Field that gives you access to the key data in the results.
This is the main part that I'm looking for comments on.
There are 2 dependencies for this code: JDOM and Commons HttpClient. I'll
remove the JDOM dependency in favor of regular DOM at some point, but I think
that the HttpClient dependency is worthwhile here. There's a lot that can be
exploited with HttpClient that isn't demonstrated in this class. The purpose
here is mainly to get feedback on the API of SolrSearcher before I start
optimizing anything.
--
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
