(calcite-site) branch main updated: Website deployed from calcite@648a832e0b3abc0f1cd4887847bdef7c133cb383

[as...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

asf-ci-deploy pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/calcite-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 03d3216b3 Website deployed from calcite@648a832e0b3abc0f1cd4887847bdef7c133cb383
03d3216b3 is described below

commit 03d3216b3218f317ddb49337564a66fd6c14ed84
Author: zabetak <za...@users.noreply.github.com>
AuthorDate: Thu Dec 19 09:47:42 2024 +0000

    Website deployed from calcite@648a832e0b3abc0f1cd4887847bdef7c133cb383
---
 docs/history.html | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/history.html b/docs/history.html
index d77d37ced..40c09234b 100644
--- a/docs/history.html
+++ b/docs/history.html
@@ -129,6 +129,17 @@ this behavior.  The BIG_QUERY and SQL_SERVER_2008 conformance have
 been changed to use checked arithmetic, matching the specification of
 these dialects.
 
+* [<a href="https://issues.apache.org/jira/browse/CALCITE-6704">CALCITE-6704</a>]
+Limit result size of `RelMdUniqueKeys` handler. Certain query patterns can lead
+to an exponentially large number of unique keys that can cause crashes and OOM
+errors. To prevent this kind of issues the `RelMdUniqueKeys` handler is now using
+a limit to restrict the number of keys for each relational expression. The limit
+is set to `1000` by default. The value is reasonably large to ensure that
+most common use-cases will not be affected and at the same time bounds exponentially
+large results set to a manageable value. Users that need a bigger/smaller limit
+should create a new instance of `RelMdUniqueKeys` and register it using the
+metadata provider of their choice.
+
 #### New features
 {: #new-features-1-39-0}