- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Your issue seems like a bug or some kind of limitation in Amazon Neptune SPARQL engine that isn't properly handled. Normally, RDF stores have limits in terms of the size of the literals they can handle, but these limits are usually documented and result in more informative error messages.
You mentioned a few possible causes in your description:
-
Size of the JSON object: You noticed that reducing the size of your JSON object significantly caused the query to succeed on both databases. It might be possible that the size of the JSON object is causing an error.
-
Different regions: It's also possible that the difference in behavior between the two databases is related to them being in different regions, although this would be unusual.
Here are few suggestions to further debug the issue:
-
Size limit: Try to gradually reduce the size of your JSON literal to see if there's a specific limit where the error occurs. This could give you an indication of whether there's a specific size limit.
-
JSON complexity: It's also possible that the complexity of the JSON object (in terms of nested objects, arrays, etc.) could be causing the error. Try simplifying the JSON object to see if that resolves the issue.
-
Contact AWS Support: If the above strategies do not work, I would recommend reaching out to AWS support. They have access to more detailed logs and internal metrics and can potentially provide more insight into the issue.
Keep in mind that handling large JSON literals in RDF triples might not be the best practice. If you find that the size of the JSON object is the issue, you might want to consider a different data modeling approach. For instance, you could represent your JSON data as a collection of smaller triples rather than one large JSON literal.
Contenuto pertinente
- AWS UFFICIALEAggiornata 4 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
Thanks for reporting this @adlerfaulkner. We are doing some investigating.