App cannot be started due to "MapperParsingException"

[dr0i]

Oops, cannot start the server.
ElasticsearchException[Bulk insert failed: failure in bulk execution:
[8844]: index [organisations], type [organisation], id [DBS-XY123], message [MapperParsingException[failed to parse]; nested: ElasticsearchParseException[field [lat] missing];]]
at controllers.Index.indexData(Index.java:212)

[dr0i]

From the data that failed to be indexed:

enriched.prod.out.json-dbs:{"rs":"055150000000","type":"Library","[...]"geo":{"lon":"7.633706"},"type":"Place"}],

Clearly, there is the geo.lat missing.
@TobiasNx could you fix this with setting a dummy fro geo.lator (better?) dump the whole geo entry if one of lat or lon is missing?

[TobiasNx]

When I test this locally there seems to be no error. This is an error because of the pelias lookup which only seems to have an lon but no lat which is strange.

General question how is pelias build and should we update it? Also because of #476 and #483
Otherwise workaround as you suggested would work fine.

if exists("latDbs")
	copy_field("latDbs","@visitorLocation.geo.lat") # <!-- dbs verzeichnis -->
elsif exists("latVisitor")
	copy_field("latVisitor","@visitorLocation.geo.lat") # <!-- zdb sigel verzeichnis -->
elsif exists("@geoLookupDbs") # <!-- geo lookup pelias -->
	copy_field("@geoLookupDbs","@geoLookupDbsLat")
	lookup("@geoLookupDbsLat","addLatMap", delete:"true")
	copy_field("@geoLookupDbsLat","@visitorLocation.geo.lat")
end

if exists("lonDbs")
	copy_field("lonDbs","@visitorLocation.geo.lon") # <!-- dbs verzeichnis -->
elsif exists("lonVisitor") 
	copy_field("lonVisitor","@visitorLocation.geo.lon") # <!-- zdb sigel verzeichnis -->
elsif exists("@geoLookupDbs")
	copy_field("@geoLookupDbs","@geoLookupDbsLon")
	lookup("@geoLookupDbsLon","addLongMap" , delete:"true") # <!-- geo lookup pelias -->
	copy_field("@geoLookupDbsLon","@visitorLocation.geo.lon")
end

[dr0i]

re pelias: as discussed offline we will not look into it.

[dr0i]

Thx for the fast fix!
Note: Interestingly, the error was caused by dbsID:DBS-XY123. And this resource now has it's geo coordinate: http://lobid.org/organisations/DBS-XY123.json .

[dr0i]

Closing as solved..