[jira] [Commented] (OAK-8926) add RDBBlobStore performance test
[ https://issues.apache.org/jira/browse/OAK-8926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063815#comment-17063815 ] Julian Reschke commented on OAK-8926: - ...all information is there, if you want to try... bq. A more likely reason for the SQL Server performance is that the clustered index (the physical ordering of the table) is the ID column, and the ID values are non-sequential. Yes, that's the case. > add RDBBlobStore performance test > - > > Key: OAK-8926 > URL: https://issues.apache.org/jira/browse/OAK-8926 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.26.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OAK-8918) RDBBlobStore: warn when legacy (SQLServer) default collation is active
[ https://issues.apache.org/jira/browse/OAK-8918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063814#comment-17063814 ] Julian Reschke commented on OAK-8918: - Understood; the change was meant to be as simple as possible in order to get diagnostics. In a perfect world, this information would be available as JDBC metadata, but it's not. Feel free to open a separate ticket. > RDBBlobStore: warn when legacy (SQLServer) default collation is active > -- > > Key: OAK-8918 > URL: https://issues.apache.org/jira/browse/OAK-8918 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_8 > Fix For: 1.26.0, 1.10.9, 1.22.2 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
