[jira] Commented: (SOLR-79) [PATCH] Using system properties in Solr configuration
[
http://issues.apache.org/jira/browse/SOLR-79?page=comments#action_12457627 ]
Alexander Saar commented on SOLR-79:
I took the {$system.prop} pattern from Avalon configuration style. After having
a look at the ant way, I would also prefer ${system.prop}.
Furthermore I think it will be very helpful to have something like
${system.prop}/bin. Actually it was not my use case, but I'm sure that it is
helpful for somebody.
[PATCH] Using system properties in Solr configuration
-
Key: SOLR-79
URL: http://issues.apache.org/jira/browse/SOLR-79
Project: Solr
Issue Type: New Feature
Reporter: Alexander Saar
Priority: Minor
Attachments: solr-config-system-property.patch,
solr-config-system-property.patch
Actually it is not possible to use system properties for configuring the Solr
engine. There should be a way of referencing system properties from
solrconfig.xml, like {$prop.name}.
The attached patch will provide this feature.
--
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-79) [PATCH] Using system properties in Solr configuration
[PATCH] Using system properties in Solr configuration
-
Key: SOLR-79
URL: http://issues.apache.org/jira/browse/SOLR-79
Project: Solr
Issue Type: New Feature
Reporter: Alexander Saar
Priority: Minor
Attachments: solr-config-system-property.patch
Actually it is not possible to use system properties for configuring the Solr
engine. There should be a way of referencing system properties from
solrconfig.xml, like {$prop.name}.
The attached patch will provide this feature.
--
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-79) [PATCH] Using system properties in Solr configuration
[ http://issues.apache.org/jira/browse/SOLR-79?page=all ]
Alexander Saar updated SOLR-79:
---
Attachment: solr-config-system-property.patch
Patch that allows usage of references to system properties in the solrconfig.xml
[PATCH] Using system properties in Solr configuration
-
Key: SOLR-79
URL: http://issues.apache.org/jira/browse/SOLR-79
Project: Solr
Issue Type: New Feature
Reporter: Alexander Saar
Priority: Minor
Attachments: solr-config-system-property.patch
Actually it is not possible to use system properties for configuring the Solr
engine. There should be a way of referencing system properties from
solrconfig.xml, like {$prop.name}.
The attached patch will provide this feature.
--
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
Refactoring request
Hello, I've implemented a customized JSON Response writer. But I had to copy the code of the existing JSONResponseWriter, because I wanted to reuse the existing JSONWriter as super class. The currently used JSONWriter is a nested class, which can not be overwritten by subclasses. Is it possible to refactor it to its own class file. It nobody has problems with that, I can make it and supply an according patch to the JIRA. Regards, Alex -- Alexander Saar Mindquarry - achieving more together (http://www.mindquarry.com) E-Mail: [EMAIL PROTECTED] | Mindquarry GmbH Work: +49 331 97992 223 | August-Bebel-Str. 88 Mobile: +49 177 59 85 437 | 14482 Potsdam, Germany Weblog: http://alexsaar.blogspot.com/ OpenBC Profile: http://www.openbc.com/hp/Alexander_Saar/
Re: Refactoring request
It does nothing really different than the existing JSON writer. But I need to transform the content of some fields like URLs for indexed documents. These URLs are posted to the index by another component I can't change, so I have to do the transformation on the results of a query. I'm sure this can also be done with JavaScript, but I think it is easier to do it with Java. Regards, Alex Erik Hatcher schrieb: Alex, I'm curious what your customized writer does differently. Care to elaborate? Thanks, Erik On Dec 8, 2006, at 10:30 AM, Alexander Saar wrote: Hello, I've implemented a customized JSON Response writer. But I had to copy the code of the existing JSONResponseWriter, because I wanted to reuse the existing JSONWriter as super class. The currently used JSONWriter is a nested class, which can not be overwritten by subclasses. Is it possible to refactor it to its own class file. It nobody has problems with that, I can make it and supply an according patch to the JIRA. Regards, Alex --Alexander Saar Mindquarry - achieving more together (http://www.mindquarry.com) E-Mail: [EMAIL PROTECTED] | Mindquarry GmbH Work: +49 331 97992 223 | August-Bebel-Str. 88 Mobile: +49 177 59 85 437 | 14482 Potsdam, Germany Weblog: http://alexsaar.blogspot.com/ OpenBC Profile: http://www.openbc.com/hp/Alexander_Saar/ -- Alexander Saar (CTO) Mindquarry - achieving more together (http://www.mindquarry.com) E-Mail: [EMAIL PROTECTED] | Mindquarry GmbH Work: +49 331 97992 223 | August-Bebel-Str. 88 Mobile: +49 177 59 85 437 | 14482 Potsdam, Germany Weblog: http://alexsaar.blogspot.com/ OpenBC Profile: http://www.openbc.com/hp/Alexander_Saar/
Config Loading Improvement
Hello, I recently started integrating Solr as Cocoon Block into our application. While doing this I noticed that there is a problem with loading the Solr configuration in Config.getVal(). It throws an UnsupportedOperationException when Node.getTextContent() is called when I run it in our Cocoon development environment, which is based on Jetty Maven Plugin. I think this is due older parser version which does not implement getTextContent for the Node type. So far I created a patch that should work for actual and older implementations of the DOM API. While searching the JIRA, I did not find any issues that refers to this problem (while there is a comment in the code about it). So my question is: is anybody else working on this problem or is this not really a problem and I did something wrong? If this seems to be a good improvement, I can supply a patch to the JIRA. Regards, Alex -- Alexander Saar Mindquarry - achieving more together (http://www.mindquarry.com) E-Mail: [EMAIL PROTECTED] | Mindquarry GmbH Work: +49 331 97992 223 | August-Bebel-Str. 88 Mobile: +49 177 59 85 437 | 14482 Potsdam, Germany Weblog: http://alexsaar.blogspot.com/ OpenBC Profile: http://www.openbc.com/hp/Alexander_Saar/
[jira] Created: (SOLR-78) [PATCH] Improved config loading
[PATCH] Improved config loading --- Key: SOLR-78 URL: http://issues.apache.org/jira/browse/SOLR-78 Project: Solr Issue Type: Improvement Reporter: Alexander Saar Priority: Minor Solr configuration throws an UnsupportedConfigurationException for Node.getTextContent() if it is started in server environments that uses older implementations of the DOM API. This can be improved by checking wich node type is actually handled an calling the appropriate methods. A patch that fixes this problem is attached. -- 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-78) [PATCH] Improved config loading
[ http://issues.apache.org/jira/browse/SOLR-78?page=all ] Alexander Saar updated SOLR-78: --- Attachment: fixed-config-loading-with-older-parser-versions.patch Patch that fixes the problem described by this issue. [PATCH] Improved config loading --- Key: SOLR-78 URL: http://issues.apache.org/jira/browse/SOLR-78 Project: Solr Issue Type: Improvement Reporter: Alexander Saar Priority: Minor Attachments: fixed-config-loading-with-older-parser-versions.patch Solr configuration throws an UnsupportedConfigurationException for Node.getTextContent() if it is started in server environments that uses older implementations of the DOM API. This can be improved by checking wich node type is actually handled an calling the appropriate methods. A patch that fixes this problem is attached. -- 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
