docs/src/main/sphinx/release/release-360.md
GROUP BY or LIMIT and
complex correlated filter conditions. ({issue}8554)8615)DROP SCHEMA and DROP SCHEMA RESTRICT not to drop then schema if it is not empty. ({issue}8660)col (e.g col=1), followed by ORDER BY col and LIMIT. ({issue}8535)SHOW CREATE SCHEMA failure. ({issue}8598)SHOW CREATE SCHEMA information_schema. ({issue}8600)WHERE clause evaluation. ({issue}8624)8460)5183)8500)IN (<subquery>) expressions. ({issue}8639)/security/internal-communication. This removes
the need to provision per-worker TLS certificates. ({issue}7954)8529)write.batch-size connector configuration property to control JDBC batch size used during writes.
It can also be controlled using the write_batch_size session property. ({issue}8434)insert.non-transactional-insert.enabled to allow INSERT queries to write directly
to the target table. This can improve performance in some cases by sacrificing transactional behaviour. It can also
be controlled using non_transactional_insert session property. ({issue}8496)8714)UPDATE or INSERT on ORC ACID transactional table. ({issue}8268, {issue}8452)8540)8450)7502)8616)array, map or row). ({issue}8647)5201)8676, {issue}8689)write.batch-size connector configuration property to control JDBC batch size used during writes.
It can also be controlled using the write_batch_size session property. ({issue}8434)insert.non-transactional-insert.enabled to allow INSERT queries to write directly
to the target table. This can improve performance in some cases by sacrificing transactional behaviour. It can also
be controlled using non_transactional_insert session property. ({issue}8496)DELETE statement where predicate can be fully pushed down to the remote datasource. ({issue}6287)8559)json type. ({issue}8352)DBRef type. ({issue}3134)write.batch-size connector configuration property to control JDBC batch size used during writes.
It can also be controlled using the write_batch_size session property. ({issue}8434)insert.non-transactional-insert.enabled to allow INSERT queries to write directly
to the target table. This can improve performance in some cases by sacrificing transactional behaviour. It can also
be controlled using non_transactional_insert session property. ({issue}8496)DELETE statement where predicate can be fully pushed down to the remote datasource. ({issue}6287)8559)write.batch-size connector configuration property to control JDBC batch size used during writes.
It can also be controlled using the write_batch_size session property. ({issue}8434)insert.non-transactional-insert.enabled to allow INSERT queries to write directly
to the target table. This can improve performance in some cases by sacrificing transactional behaviour. It can also
be controlled using non_transactional_insert session property. ({issue}8496)DELETE statement where predicate can be fully pushed down to the remote datasource. ({issue}6287)write.batch-size connector configuration property to control JDBC batch size used during writes.
It can also be controlled using the write_batch_size session property. ({issue}8434)insert.non-transactional-insert.enabled to allow INSERT queries to write directly
to the target table. This can improve performance in some cases by sacrificing transactional behaviour. It can also
be controlled using non_transactional_insert session property. ({issue}8496)ORDER BY ... LIMIT queries on sorted data for Phoenix 5. ({issue}8171)DELETE statement where predicate can be fully pushed down to the remote datasource. ({issue}6287)8559)write.batch-size connector configuration property to control JDBC batch size used during writes.
It can also be controlled using the write_batch_size session property. ({issue}8434)insert.non-transactional-insert.enabled to allow INSERT queries to write directly
to the target table. This can improve performance in some cases by sacrificing transactional behaviour. It can also
be controlled using non_transactional_insert session property. ({issue}8496)DELETE statement where predicate can be fully pushed down to the remote datasource. ({issue}6287)write.batch-size connector configuration property to control JDBC batch size used during writes.
It can also be controlled using the write_batch_size session property. ({issue}8434)insert.non-transactional-insert.enabled to allow INSERT queries to write directly
to the target table. This can improve performance in some cases by sacrificing transactional behaviour. It can also
be controlled using non_transactional_insert session property. ({issue}8496)DELETE statement where predicate can be fully pushed down to the remote datasource. ({issue}6287)write.batch-size connector configuration property to control JDBC batch size used during writes.
It can also be controlled using the write_batch_size session property. ({issue}8434)insert.non-transactional-insert.enabled to allow INSERT queries to write directly
to the target table. This can improve performance in some cases by sacrificing transactional behaviour. It can also
be controlled using non_transactional_insert session property. ({issue}8496)DELETE statement where predicate can be fully pushed down to the remote datasource. ({issue}6287)8559)8408)ConnectorSplitManager#getSplits method overrides. ({issue}8569)ConnectorPageSource#getCompletedPositions for tracing physically read positions. ({issue}8524)TupleDomain.transform. ({issue}8056)