Invalid Sense example code about elasticsearch-definitive-guide HOT 4 OPEN

Hi @w33ble

Yes... This is a tricky one. Elasticsearch can accept plain text in the body, eg:

curl localhost:9200/_analyze?analyzer=standard -d '
Text to analyze here
'

This is a much clearer syntax for explanation purposes than:

curl localhost:9200/_analyze?analyzer=standard&text=Text%20to%20analyze%20here

However, Sense can only handle JSON bodies, not plain text. With a JSON body it knows where the end of the body should be. A plain text body might include paragraphs, so where does the body actually end?

There is an open issue (elastic/elasticsearch#5866) to allow the analyze end point to accept JSON instead of text, which would solve this issue.

from elasticsearch-definitive-guide.

Cool, thanks for the feedback. Curious: is analyze the only command that's takes text instead of JSON?

from elasticsearch-definitive-guide.

No, there are the scroll and clear scroll APIs too, but those are less problematic.

from elasticsearch-definitive-guide.

Just curious how do I do scroll api in Sense then? Thanks,

from elasticsearch-definitive-guide.