jira at apache
Jul 28, 2012, 10:56 AM
Post #1 of 1
(46 views)
Permalink
|
|
[jira] [Resolved] (SOLR-358) Implement solr-ruby-specific response capability
|
|
[ https://issues.apache.org/jira/browse/SOLR-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik Hatcher resolved SOLR-358.
-------------------------------
Resolution: Won't Fix
This was a nice thought experiment, but at this point solr-ruby is mothballed and I'm not particularly interested in pushing richer types into RSolr. It's a shame that JSON, Ruby, etc are String-typed dates, but not worth the effort to battle it at this point.
> Implement solr-ruby-specific response capability
> ------------------------------------------------
>
> Key: SOLR-358
> URL: https://issues.apache.org/jira/browse/SOLR-358
> Project: Solr
> Issue Type: Improvement
> Components: clients - ruby - flare
> Reporter: Erik Hatcher
> Assignee: Erik Hatcher
> Attachments: SOLR-358.patch
>
>
> Implement solr-ruby-specific Ruby output, such that dates get created as real DateTime objects (wrap with DateTime.parse(...) is one option), and so that named lists maintain name and order access cleanly. This could be a formating option for wt=ruby, or a new writer type - suggestions welcome. This would make the richest way to access Solr from Ruby, with the standard Hash access unaffected and suitable for cases where using an additional library isn't desired.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene
|
