[
https://issues.apache.org/jira/browse/JENA-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453545#comment-17453545
]
Jean-Marc Vanel commented on JENA-2202:
---------------------------------------
Sure, I'll provide a test case.
Maybe you can point me to an existing test that I could imitate or extend .
For users of Jena 4.2.0, these SPARQL queries and SPARQL updates are useful to
detect and fix triples preventing correct geoparql (spatial) query in Jena
4.2.0 ,
which are anyway incorrect data: coordinates as strings, missing longitude:
[https://github.com/jmvanel/semantic_forms/commit/613e03c43b85d6f5774fd02c6c0ea8b3a6bb8300]
[https://github.com/jmvanel/semantic_forms/tree/master/sparql]
> Spatial Indexing can fail on malformed literals
> -----------------------------------------------
>
> Key: JENA-2202
> URL: https://issues.apache.org/jira/browse/JENA-2202
> Project: Apache Jena
> Issue Type: Bug
> Components: Spatial
> Affects Versions: Jena 4.2.0
> Reporter: Jean-Marc Vanel
> Assignee: Andy Seaborne
> Priority: Major
> Fix For: Jena 4.3.0
>
>
> Reported on mailing lists via
> https://lists.apache.org/thread/y3qx4811tyjn448qsnw8xdhjg03s2jpn
> If data being indexed for a spatial index contains malformed geo-literals a
> NPE is encountered causing indexing to abort rather than issuing a warning
> and continuing. This prevents creating a spatial index when there's invalid
> data mixed into the valid data. While users should likely be ensuring their
> data is clean the reality of real world data is that it rarely is.
> Suggested fix is to handle the case and issue a warning before continuing
> indexing.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
