Tony, (1) Your first question seems to be about the curl command. If so, then it follows shell script rules. In most Unix shell scripts, double-quotes preserve spaces and such, but allow for variable substitution. Sngle-quotes also preserve spaces but do not allow variable substitution and preserve all characters as-is. Example:
export FIELD=_all curl -XGET "http://localhost:9200/$FIELD/_mapping"; is converted by the shell to: curl -XGET http://localhost:9200/_all/_mapping curl -XGET 'http://localhost:9200/$FIELD/_mapping' is converted by the shell to: curl -XGET http://localhost:9200/$FIELD/_mapping So single quotes are usually preferred so that the & and ? characters in URL parameter lists are not interpreted as shell characters. But if you want to parameterize a curl command, you may need to use double-quotes for parts, and single-quotes for the other parts. This is all standard shell programming. (2) Camel case is OK for hostnames because hostnames are typically insensitive. But JSON and ES are case-sensitive. (3) This is a JSON standard. {"field":"name"} and { "field" : "name" } are the same, but one or the other is prettier. Brian -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/69adf245-d360-4cde-a01e-779d3e44d334%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
