gcs
gcs copied to clipboard
groonga
Groonga CloudSearch is an open source implementation of Amazon CloudSearch.
Now we don't store original documents and there are only indexed fields. To support "SourceAttribute" and "DefaultValue" behaviours, we have to store original documents separately.
Possible invalid entries: - Including unknown field in its "fields" - Including mismatched type value in its "fields": for example, string value for uint field - Without "fields" option
- http://docs.amazonwebservices.com/cloudsearch/latest/developerguide/API_UIntOptions.html - http://docs.amazonwebservices.com/cloudsearch/latest/developerguide/API_LiteralOptions.html - http://docs.amazonwebservices.com/cloudsearch/latest/developerguide/API_TextOptions.html
http://docs.amazonwebservices.com/cloudsearch/latest/developerguide/API_SourceAttribute.html
http://docs.amazonwebservices.com/cloudsearch/latest/developerguide/thresholdresults.html It is not supported yet.
Simple sorting by existing fields is implemented on #106. Custom rank expressions is not supported yet.
[aws_cloud_search](https://github.com/spokesoftware/aws_cloud_search) is strongly bound to Amazon CloudSearch. (ex. endpoint domain is hard-coded.) To use this library for Groonga CloudSearch, we have to apply some matches dynamically. Such changes should be...
If the database becomes incompatible by GCS upgrade, the gcs command should warn and stop starting.
GCS returned 400 if `"` is searched. At least, no error reported from ACS with this query. The response is like this: ``` {"rank":"-text_relevance","match-expr":"(label '\"')","hits":{"found":0,"start":0,"hit":[]},"info":{"rid":"90c9b0fdba3e834bf5a4adc5a44bb0213c6fda472737d9c72c83ead280a55a1ff45793bcc973b90f","time-ms":2,"cpu-time-ms":0}} ``` The index searched against...