Stephen Compall e5c4734780 enable JSON search index on Oracle by default (#10539) ... * unconditionally enable JSON search index on Oracle In '1kb of data' and larger Oracle integration tests: ORA-29902: error in executing ODCIIndexStart() routine ORA-20000: Oracle Text error: DRG-50943: query token too long on line 1 on column 3 From https://docs.oracle.com/en/database/oracle/oracle-database/19/errmg/DRG-10000.html#GUID-46BC3B3F-4DB7-4EB4-85DA-55E9461966CB Cause: A query token is longer than 256 bytes Action: Rewrite query * add changelog CHANGELOG_BEGIN - [JSON API] The Oracle database schema has changed; if using ``--query-store-jdbc-config``, you must rebuild the database by adding ``,start-mode=create-only``. See #10539. CHANGELOG_END * test only 1kb * extra flag in db config string * let Queries backends configure themselves from maps * new Queries constructor dataflow to better support config values * remove fields as we go, isolating backend-specific from -agnostic conf - we use StateT to avoid the problems that will definitely arise if we don't DRY. * fix up DbConfig including DbStartupMode * start to uncouple json-api's config from db-utils * two JdbcConfigs with different purposes/scopes - also moves db-utils contents to com.daml.dbutils * adapt trigger service to refactoring * fix JdbcConfig leftovers * adapt http-json-cli to new JdbcConfig * remove extra ConfigCompanion * explain more about the QueryBackend/Queries distinction * split SupportedJdbcDriver into two phases with a tparam * use SupportedJdbcDriver.TC instead of SupportedJdbcDriver as the nullary typeclass * patch around all the moved objects with imports * missed import from moving ConnectionPool to dbutils * use new 2-phase SupportedJdbcDriver for ContractDao setup * left off part of a comment * more q.queries imports * other imports from the dbutils move * nested JdbcConfig * configure the driver in each backend-specific test * very confusing error, but make the imports nicer and it goes away * nested JdbcConfig in perf * missing newline * port contractdao-bench * test new option parsing all the way through QueryBackend * disable search index for some tests, enable for others * add changelog CHANGELOG_BEGIN - [Trigger Service] ``--help`` no longer advertises unsupported JDBC options from JSON API. - [JSON API] [EE only] By default, on Oracle, sets up a JSON search index to speed up the queries endpoints. However, Oracle versions prior to 19.12 have an unrecoverably buggy implementation of this index; in addition, the current implementation fails on queries with strings >256 bytes, with no way to disable the index for that query. Pass the ``disableContractPayloadIndexing=true`` option as part of ``--query-store-jdbc-config`` to disable this index when creating the schema. See `issue #10539 <https://github.com/digital-asset/daml/pull/10539>`__. CHANGELOG_END * port failure tests * init version table last, drop first - suggested by @realvictorprm; thanks * rename split DBConfig.scala - suggested by @realvictorprm; thanks * move imports to not be in alphabetical order - suggested by @realvictorprm; thanks * remove createSchema - suggested by @realvictorprm; thanks * Revert "test only 1kb" This reverts commit 616e173e63. * port to scala 2.12 - bug in unused imports - old name `-` for `removed`		2021-08-31 09:29:36 +00:00
..
daml	Expose pending contracts in triggers (#10672)	2021-08-25 13:23:15 +00:00
runner	LF: V1 Contract ID check in Preprocessor (#10687)	2021-08-30 20:14:55 +02:00
service	enable JSON search index on Oracle by default (#10539)	2021-08-31 09:29:36 +00:00
tests	bazel-tools: Replace runner with either runner_with_port_check or runner_with_port_file. (#10615)	2021-08-18 15:23:45 +00:00