Opened 6 years ago
Closed 5 years ago
#7235 closed defect (wontfix)
Elasticsearch: add MAPPING_NAME open option
Reported by: | tomkralidis | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | closed_because_of_github_migration |
Component: | default | Version: | unspecified |
Severity: | normal | Keywords: | Elasticsearch |
Cc: |
Description
Similar to layer creation options, it would be valuable to have MAPPING_NAME
as an open option for use cases where GeoJSON is stored in an ES index but the mapping is not named FeatureCollection
.
Change History (3)
comment:1 by , 6 years ago
comment:3 by , 5 years ago
Milestone: | → closed_because_of_github_migration |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
This ticket has been automatically closed because Trac is no longer used for GDAL bug tracking, since the project has migrated to GitHub. If you believe this ticket is still valid, you may file it to https://github.com/OSGeo/gdal/issues if it is not already reported there.
Note:
See TracTickets
for help on using tickets.
I'd rather called the option MAPPING_TYPE=FeatureCollection, since the mapping name is something existing on the database side.