mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 01:07:18 +03:00
changelog_begin [Docs/JSON API] documented 256B limitation of Oracle query store changelog_end
This commit is contained in:
parent
5814f6ad9d
commit
c12f546774
@ -126,3 +126,14 @@ value equality query for C.
|
||||
The above "Typecheck failure" happens because there is no LF type to
|
||||
which both ``"Bob"`` and ``["Bob", "Sue"]`` conform; this would be
|
||||
caught when interpreting the query, before considering any contracts.
|
||||
|
||||
Appendix: Known issues
|
||||
**********************
|
||||
|
||||
When using Oracle, queries fail if a token is too large
|
||||
=======================================================
|
||||
|
||||
This limitation is exclusive to users of the HTTP JSON API using the Enterprise Edition support for Oracle. Due to a known limitation in Oracle, the full-test JSON search index on the contract payloads rejects query tokens larger than 256 bytes. This limitations shouldn't impact most workloads, but if this needs to be worked around, the HTTP JSON API server can be started passing the additional ``disableContractPayloadIndexing=true`` (after wiping an existing query store database, if necessary).
|
||||
|
||||
`Issue on GitHub <https://github.com/digital-asset/daml/issues/10780>`__
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user