[Maps] Error on uploading a medium GeoJSON

[jsanz]

Kibana version: 7.3.1

Elasticsearch version: 7.3.1

Server OS version: Elastic Cloud

Browser version: Chrome Version 76.0.3809.136 (Official Build) (64-bit)

Browser OS version: Chrome OS Version 76.0.3809.136 (Official Build) (64-bit)

Original install method (e.g. download page, yum, from source, etc.): Elastic Cloud

Describe the bug: Index creation from a GeoJSON upload hangs after processing the file in the browser.

Steps to reproduce:

1. Get this GML file from Spanish Cadastre and unzip

$ curl -O "http://www.catastro.minhap.es/INSPIRE/Buildings/46/46900-VALENCIA/A.ES.SDGC.BU.46900.zip"
$ unzip A.ES.SDGC.BU.46900.zip

2. Convert to GeoJSON stripping some fields and adjusting precision to reduce file size

$ ogr2ogr -f GeoJSON -t_srs "EPSG:4326" -lco "COORDINATE_PRECISION=7"  \
-sql "select beginLifespanVersion as life_begin, conditionOfConstruction as condition, reference as ref, currentUse, numberOfBuildingUnits as b_units, numberOfDwellings as dwelings, officialAreaReference as area_reference, value as area_value, value_uom as area_uom, endLifespanVersion as life_end from Building"  \
buildings-46900-mini.geo.json A.ES.SDGC.BU.46900.building.gml

3. Open a new Maps session and upload buildings-46900-mini.geo.json
4. An index is generated but not populated

GET /buildings-46900-mini/_mapping

{
  "buildings-46900-mini" : {
    "mappings" : {
      "_meta" : {
        "created_by" : "file-upload-plugin"
      },
      "properties" : {
        "coordinates" : {
          "type" : "geo_shape"
        }
      }
    }
  }
}

Expected behavior: The index is populated and ready to continue with the layer workflow

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context: I can provide a full HAR file if needed.

[elasticmachine]

Pinging @elastic/kibana-gis

[jsanz]

This should be easy to replicate on a dev environment, which unfortunately I can't set up yet 😞, I wonder if it's more an issue with Elastic Cloud itself, given the 413 response.

Forgot to mention the GeoJSON file I tried to upload is around 38MB.

[thomasneirynck]

Putting a 7.5.0 label on this, as Geojson is going GA then. This is a small file, under the range we expect. Perhaps recent improvements resolve this.

cc @aaronjcaldwell