[
https://issues.apache.org/jira/browse/XERCESJ-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623086#comment-16623086
]
Mukul Gandhi commented on XERCESJ-1701:
---------------------------------------
As far as I know, XercesJ doesn't use a hash store currently, to evaluate XSD
IDC constraints. Using a hash store, for IDC constraint implementation would be
a significant change in design. Therefore, it must be done carefully (existing
behavior must be preserved, along with solving the current problem).
@Yitzhak, can you try writing a patch for us? If you decide to, please also
look at XERCESJ-1276 which seems to discuss the same problem. Some patches have
been proposed, in the jira issue XERCESJ-1276, that also need to be evaluated I
think for this jira issue.
If someone, can evaluate all improvements suggested in XERCESJ-1276, and
recommend if we can use any of them, along with a latest patch for Xerces
2.12.0 version, that would be great. Along with a latest patch, couple of test
cases would also be helpful.
> Xerces-J 2.12.0: XSD 1.1 PK constraint scalability issue
> --------------------------------------------------------
>
> Key: XERCESJ-1701
> URL: https://issues.apache.org/jira/browse/XERCESJ-1701
> Project: Xerces2-J
> Issue Type: Bug
> Components: JAXP (javax.xml.validation)
> Affects Versions: 2.12.0
> Environment: Windows 10, 64-bit
> Reporter: Yitzhak Khabinsky
> Priority: Major
> Labels: XSD, key
> Fix For: 2.12.0
>
> Attachments: SubscriberCountFact.zip
>
>
> Hello,
> A test case is very simple:
> * XML file, size 700 MB
> * XSD file
> XSD is enforcing the following:
> * XML structure
> * Data elements/attributes data types
> * *PK constraint, composite primary key based on four elements*
> * No asserts/assertions/CTAs
> <xs:key name="PK">
> <xs:selector xpath="r"/>
> <xs:field xpath="CountryCode"/>
> <xs:field xpath="Date"/>
> <xs:field xpath="AnalyticsArrangementKey"/>
> <xs:field xpath="PaymentType"/>
> </xs:key>
>
> Saxon Java EE runs XSD validation for 2 minutes
> Xerces-J 2.12.0 cannot finish it at all, running for many hours.
> If I comment out the *xs:key* constraint, Xerces has no problems to finish
> the validation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]