[ 
https://issues.apache.org/jira/browse/SOLR-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Høydahl updated SOLR-2202:
------------------------------

    Description: 
Provides support for monetary values to Solr/Lucene with query-time currency 
conversion. The following features are supported:

- Point queries
- Range quries
- Sorting
- Currency parsing by either currency code or symbol.
- Symmetric & Asymmetric exchange rates. (Asymmetric exchange rates are useful 
if there are fees associated with exchanging the currency.)

At indexing time, money fields can be indexed in a native currency. For 
example, if a product on an e-commerce site is listed in Euros, indexing the 
price field as "1000,EUR" will index it appropriately. By altering the 
currency.xml file, the sorting and querying against Solr can take into account 
fluctuations in currency exchange rates without having to re-index the 
documents.

The new "money" field type is a polyfield which indexes two fields, one which 
contains the amount of the value and another which contains the currency code 
or symbol. The currency metadata (names, symbols, codes, and exchange rates) 
are expected to be in an xml file which is pointed to by the field type 
declaration in the schema.xml.

The current patch is factored such that Money utility functions and 
configuration metadata lie in Lucene (see MoneyUtil and CurrencyConfig), while 
the MoneyType and MoneyValueSource lie in Solr. This was meant to mirror the 
work being done on the spacial field types.

This patch will be getting used to power the international search capabilities 
of the search engine at Etsy.

Also see WIKI page: http://wiki.apache.org/solr/MoneyFieldType


  was:
Attached please find patches to add support for monetary values to Solr/Lucene 
with query-time currency conversion. The following features are supported:

- Point queries (ex: "price:4.00USD")
- Range quries (ex: "price:[$5.00 TO $10.00]")
- Sorting.
- Currency parsing by either currency code or symbol.
- Symmetric & Asymmetric exchange rates. (Asymmetric exchange rates are useful 
if there are fees associated with exchanging the currency.)

At indexing time, money fields can be indexed in a native currency. For 
example, if a product on an e-commerce site is listed in Euros, indexing the 
price field as "10.00EUR" will index it appropriately. By altering the 
currency.xml file, the sorting and querying against Solr can take into account 
fluctuations in currency exchange rates without having to re-index the 
documents.

The new "money" field type is a polyfield which indexes two fields, one which 
contains the amount of the value and another which contains the currency code 
or symbol. The currency metadata (names, symbols, codes, and exchange rates) 
are expected to be in an xml file which is pointed to by the field type 
declaration in the schema.xml.

The current patch is factored such that Money utility functions and 
configuration metadata lie in Lucene (see MoneyUtil and CurrencyConfig), while 
the MoneyType and MoneyValueSource lie in Solr. This was meant to mirror the 
work being done on the spacial field types.

This patch has not yet been deployed to production but will be getting used to 
power the international search capabilities of the search engine at Etsy.





Updated description, as it was a bit outdated
                
> Money FieldType
> ---------------
>
>                 Key: SOLR-2202
>                 URL: https://issues.apache.org/jira/browse/SOLR-2202
>             Project: Solr
>          Issue Type: New Feature
>          Components: Schema and Analysis
>    Affects Versions: 1.5
>            Reporter: Greg Fodor
>            Assignee: Jan Høydahl
>             Fix For: 3.6, 4.0
>
>         Attachments: SOLR-2022-solr-3.patch, SOLR-2202-lucene-1.patch, 
> SOLR-2202-solr-1.patch, SOLR-2202-solr-2.patch, SOLR-2202-solr-4.patch, 
> SOLR-2202-solr-5.patch, SOLR-2202-solr-6.patch, SOLR-2202-solr-7.patch, 
> SOLR-2202-solr-8.patch, SOLR-2202-solr-9.patch, SOLR-2202.patch, 
> SOLR-2202.patch, SOLR-2202.patch
>
>
> Provides support for monetary values to Solr/Lucene with query-time currency 
> conversion. The following features are supported:
> - Point queries
> - Range quries
> - Sorting
> - Currency parsing by either currency code or symbol.
> - Symmetric & Asymmetric exchange rates. (Asymmetric exchange rates are 
> useful if there are fees associated with exchanging the currency.)
> At indexing time, money fields can be indexed in a native currency. For 
> example, if a product on an e-commerce site is listed in Euros, indexing the 
> price field as "1000,EUR" will index it appropriately. By altering the 
> currency.xml file, the sorting and querying against Solr can take into 
> account fluctuations in currency exchange rates without having to re-index 
> the documents.
> The new "money" field type is a polyfield which indexes two fields, one which 
> contains the amount of the value and another which contains the currency code 
> or symbol. The currency metadata (names, symbols, codes, and exchange rates) 
> are expected to be in an xml file which is pointed to by the field type 
> declaration in the schema.xml.
> The current patch is factored such that Money utility functions and 
> configuration metadata lie in Lucene (see MoneyUtil and CurrencyConfig), 
> while the MoneyType and MoneyValueSource lie in Solr. This was meant to 
> mirror the work being done on the spacial field types.
> This patch will be getting used to power the international search 
> capabilities of the search engine at Etsy.
> Also see WIKI page: http://wiki.apache.org/solr/MoneyFieldType

--
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to