[
https://issues.apache.org/jira/browse/SOLR-7216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-7216:
---
Description:
hhttp://yonik.com/solr-json-request-api/
The drawbacks to only having a query-parameter API include:
- Inherently un-structured, requiring unsightly parameters like
f.facet_name.facet.range.start=5
- Inherently un-typed… everything is a string.
- More difficult to decipher large requests.
- Harder to programmatically create a request.
- Impossible to validate. Because of the lack of structure, we don’t know the
set of valid parameter and thus can’t do good error checking.
was:
http://heliosearch.org/heliosearch-solr-json-request-api/
The drawbacks to only having a query-parameter API include:
- Inherently un-structured, requiring unsightly parameters like
f.facet_name.facet.range.start=5
- Inherently un-typed… everything is a string.
- More difficult to decipher large requests.
- Harder to programmatically create a request.
- Impossible to validate. Because of the lack of structure, we don’t know the
set of valid parameter and thus can’t do good error checking.
JSON Request API
Key: SOLR-7216
URL: https://issues.apache.org/jira/browse/SOLR-7216
Project: Solr
Issue Type: New Feature
Reporter: Yonik Seeley
hhttp://yonik.com/solr-json-request-api/
The drawbacks to only having a query-parameter API include:
- Inherently un-structured, requiring unsightly parameters like
f.facet_name.facet.range.start=5
- Inherently un-typed… everything is a string.
- More difficult to decipher large requests.
- Harder to programmatically create a request.
- Impossible to validate. Because of the lack of structure, we don’t know the
set of valid parameter and thus can’t do good error checking.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
