You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@rya.apache.org by "Aaron Mihalik (JIRA)" <ji...@apache.org> on 2017/07/19 16:05:00 UTC

[jira] [Commented] (RYA-316) Long LineStrings break MongoDB ingest

    [ https://issues.apache.org/jira/browse/RYA-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093325#comment-16093325 ] 

Aaron Mihalik commented on RYA-316:
-----------------------------------

[~Pujav65][~meiercaleb@gmail.com]

The issue is when Mongo ties to put the Object/literal into the PO and OS indices.  The index keys are way too long.

Unfortunately, I can't figure out obvious way around this.  Mongo can do hash indices (awesome!), but cannot do that over compound keys (ugh).

I would like to make this solution as general purpose as possible.  I think we might have to truncate the values that we put in the index.  Or we might roll our own hash index.

--Aaron

> Long LineStrings break MongoDB ingest
> -------------------------------------
>
>                 Key: RYA-316
>                 URL: https://issues.apache.org/jira/browse/RYA-316
>             Project: Rya
>          Issue Type: Bug
>          Components: dao
>            Reporter: Aaron Mihalik
>            Assignee: Andrew Smith
>
> MongoDB will reject statements they contain very long linestrings.  Basically, the mongodb index key is limited to 1024 chars, so the insert will fail if the literal is longer.
> [Here is some example code|https://github.com/amihalik/rya-mongo-debugging/blob/master/src/main/java/com/github/amihalik/rya/mongo/debugging/linestring/LoadLineString.java].  I think the inserts will work if you use 10 points, but fail if you use linestrings with 100 points.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)