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

ASF GitHub Bot commented on RYA-316:
------------------------------------

Github user amihalik commented on a diff in the pull request:

    https://github.com/apache/incubator-rya/pull/199#discussion_r132242206
  
    --- Diff: 
dao/mongodb.rya/src/main/java/org/apache/rya/mongodb/dao/SimpleMongoDBStorageStrategy.java
 ---
    @@ -53,8 +54,11 @@
         public static final String OBJECT_TYPE_VALUE = 
XMLSchema.ANYURI.stringValue();
         public static final String CONTEXT = "context";
         public static final String PREDICATE = "predicate";
    -    public static final String OBJECT = "object";
    +    public static final String PREDICATE_HASH = "predicate_hash";
    +    public static final String OBJECT = "object_original";
    --- End diff --
    
    @pujav65 I'm concerned about index size.  please hash everything.  If you 
want another ticket for "please hash everything" I'm fine with that, but let's 
knock that out while @isper3at is cleaning this stuff up.  Key thing with mongo 
is to get the index to fit in memory, so lets do that.


> 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)

Reply via email to