SQL: Handling of coerced WKT polygons

[imotov]

WKT parser in SQL cannot handle polygons that were represented in WKT and are not closed, which can be stored if coerce flag in mapping is set to true but then cannot be retrieved in SQL. That's not an issue for polygons stored in GeoJSON. To reproduce:

DELETE test

PUT test 
{
  "mappings": {
    "properties": {
      "shape": {
        "type": "geo_shape",
        "coerce": true
      }
    }
  }
}

PUT test/_doc/1
{
  "shape": "POLYGON ((1 1, -1 1, -1 -1, 1 -1))"
}

POST _sql
{
  "query": "SELECT * FROM test"
}

The last command will return an error:

{
  "error": {
    "root_cause": [
      {
        "type": "illegal_argument_exception",
        "reason": "first and last points of the linear ring must be the same (it must close itself): lats[0]=1.0 lats[3]=-1.0 lons[0]=1.0 lons[3]=1.0"
      }
    ],
    "type": "illegal_argument_exception",
    "reason": "first and last points of the linear ring must be the same (it must close itself): lats[0]=1.0 lats[3]=-1.0 lons[0]=1.0 lons[3]=1.0"
  },
  "status": 400
}

[elasticmachine]

Pinging @elastic/es-analytics-geo

[elasticmachine]

Pinging @elastic/es-search