You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Gengliang Wang (Jira)" <ji...@apache.org> on 2024/02/02 19:56:00 UTC

[jira] [Resolved] (SPARK-46964) Change the signature of the hllInvalidLgK query execution error to take an integer as 4th argument

     [ https://issues.apache.org/jira/browse/SPARK-46964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gengliang Wang resolved SPARK-46964.
------------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Issue resolved by pull request 44995
[https://github.com/apache/spark/pull/44995]

> Change the signature of the hllInvalidLgK query execution error to take an integer as 4th argument
> --------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-46964
>                 URL: https://issues.apache.org/jira/browse/SPARK-46964
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 4.0.0
>            Reporter: Menelaos Karavelas
>            Assignee: Menelaos Karavelas
>            Priority: Trivial
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>
> The current signature of the {{hllInvalidLgK}} query execution error takes four arguments:
>  # The SQL function (a string).
>  # The minimum possible {{lgk}} value (an integer).
>  # The maximum possible {{lgk}} value (an integer).
>  # The actual invalid {{lgk}} value (a string).
> There is no meaningful reason for the 4th argument to be a string. This issue is about changing the 4th argument to an integer.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org