Hi guys, I have a generic question about having large strings as objects in triples. It is not entirely clear to me what the ramifications are if TDB indexes triples with very large objects (typically of some string type). We currently have an internal discussion about this because it seems that in the past we essentially blocked triples with a very large string object to end up in TDB in the first place (right now, the artificial limit is a string length of 1024). In most cases, clients would not put any fancy filters on such large strings in their sparql query, but they would still want to retrieve the large string object. Still, even in this use-case, it is not clear how this would negatively affect the performance both in terms of memory and cpu.
thanks Simon
