null+****@clear*****
null+****@clear*****
2012年 7月 3日 (火) 12:19:06 JST
Yoji SHIDARA 2012-07-03 12:19:06 +0900 (Tue, 03 Jul 2012) New Revision: ecfa559eefa20d500b389878ddd718aacdcf603f https://github.com/groonga/gcs.groonga.org/commit/ecfa559eefa20d500b389878ddd718aacdcf603f Log: Write about search api restrictions Modified files: restrictions/index.md Modified: restrictions/index.md (+14 -0) =================================================================== --- restrictions/index.md 2012-07-03 12:11:28 +0900 (564f71d) +++ restrictions/index.md 2012-07-03 12:19:06 +0900 (e838b64) @@ -14,3 +14,17 @@ layout: default * Multiple values (given as an array) is not available on a field. * XML SDF is not available. * XML type response is not available. + +## search API + + * Always search results are returned as a JSON. + * Always top 10 fields are returned. + * Always all fields are returned. + * Customizing fields, pagination, sorting, and XML-based response of the search API are not supported yet. + * XML responses are not supported yet. + * ```bq``` parameter http://docs.amazonwebservices.com/cloudsearch/latest/developerguide/booleansearch.html is not supported. + * Regarding ```info``` object in response: + * ```rid``` is always ```"000000000000000000000000000000000000000000000000000000000000000"```. + * ```cpu-time-ms ``` is always ```0```. + * Some queries may produce responses not compatible with ACS. This restriction comes from the differences of the query interpretation between groonga's ```match``` parameter of ```select``` command and ACS ```q``` parameter. For example, the queries which have ```:```, ```>```, ```<``` and ```|``` will not work as ACS. + * ```match-expr``` is always ```''``` -------------- next part -------------- HTML$B$NE:IU%U%!%$%k$rJ]4I$7$^$7$?(B...下载
