RDNG Attribute size limit (1024 characters)
Paul Marshall (15●1●4)
| asked Jan 09 '17, 11:18 a.m.
retagged Jan 23 '18, 6:52 a.m. by Minakshi Jaint (511●3) I have attributes that contain > 1024 characters. While the data is there (you can see it when opening the artifact)...it is not displayed in the view column. A user wouldn't know the data is there by seeing it in the view. Nor is it exported to CSV (even though it was imported with CSV). This makes CSV export a bit worthless if we don't know when data doesn't exist...or is it just > 1024 characters. Is there a work-around or fix? |
One answer
See this post.
Note: By default, JFS indexing excludes strings that are longer than approximately 1023 characters. Strings of less than 200 characters are usually allowed. You can change string length limits that are eligible for indexing. The property to change is Maximum RDF literal size. The property is located on the JTS server admin page, on the Advanced Properties page, in the com.ibm.team.jfs.indexing.service.internal.HttpIndexingService section.Basically, attributes with value longer than 1024 characters will not make it into the index, so that a SPARQL query will not get it either. When you open a single artifact, the values are retrieved from the database, so you can see them all. But you still need to set a limit there. If the attribute holds a value extremely long, probably you should consider putting it into the Primary Text? |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.