[ 
https://issues.apache.org/jira/browse/TINKERPOP3-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette closed TINKERPOP3-756.
---------------------------------------
    Resolution: Implemented
      Assignee: stephen mallette

{{GraphMLReader}} now has a {{strict}} option on the {{Builder}} so that if a 
data type for a value is invalidate in some way, {{GraphMLReader}} will simply 
skip that problem value.  In that way, it is a bit more forgiving than before 
especially with empty data.  

Implemented via:

https://github.com/apache/incubator-tinkerpop/commit/45023be9d71e565338da44aa7dbbbbd6708d2afb

> Provide a strict parsing option for GraphMLReader
> -------------------------------------------------
>
>                 Key: TINKERPOP3-756
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-756
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: io
>    Affects Versions: 3.0.0-incubating
>            Reporter: Kelvin R. Lawrence
>            Assignee: stephen mallette
>            Priority: Minor
>             Fix For: 3.1.0-incubating
>
>
> Opening this per the request of Stephen M. over on the gremlin users forum.
> https://groups.google.com/forum/#!topic/gremlin-users/jHFE7Isk61E
> If the type of a value in a GraphML file is specified as Double but the file 
> contains an empty string in that element, a rather misleading exception is 
> thrown that does not make it clear the XML file is the problem during the 
> loading of the XML using the GraphML reader.
> Stephen and I discussed a bit whether the exception text should just be 
> improved or if the behavior should be changed (ie continue loading but issue 
> a warning etc.)
> As a side note, other GraphML implementations I tried, like Gephi, handle my 
> XML file differently. Gephi loads the file and just does not assign any value 
> to the properties that contain empty strings. That's not to say Gephi is 
> right more observing this seems to be an area that is handled inconsistently 
> across GraphML readers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to