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

gurwls223 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/master by this push:
     new 128a991ba2d [SPARK-44154][SQL][FOLLOWUP] Add `INVALID_BITMAP_POSITION` 
error into doc
128a991ba2d is described below

commit 128a991ba2d8aa6bcf45b1de823a511bfa550650
Author: Hyukjin Kwon <[email protected]>
AuthorDate: Thu Jul 6 11:12:00 2023 +0900

    [SPARK-44154][SQL][FOLLOWUP] Add `INVALID_BITMAP_POSITION` error into doc
    
    ### What changes were proposed in this pull request?
    
    This is a followup PR for https://github.com/apache/spark/pull/41623, 
because we add test for sync doc and `error-classes.json` after 
https://github.com/apache/spark/pull/41813 . We should add 
`INVALID_BITMAP_POSITION` (add on https://github.com/apache/spark/pull/41623) 
into doc.
    
    ### Why are the changes needed?
    
    CI fails without this PR.
    
    ### Does this PR introduce _any_ user-facing change?
    No
    
    ### How was this patch tested?
    Existing test.
    
    Closes #41870 from HyukjinKwon/SPARK-44154.
    
    Authored-by: Hyukjin Kwon <[email protected]>
    Signed-off-by: Hyukjin Kwon <[email protected]>
---
 docs/sql-error-conditions.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/sql-error-conditions.md b/docs/sql-error-conditions.md
index 1b799ed7b67..b069f694ff3 100644
--- a/docs/sql-error-conditions.md
+++ b/docs/sql-error-conditions.md
@@ -738,6 +738,12 @@ The boundary `<boundary>` is invalid: `<invalidValue>`.
 
  For more details see 
[INVALID_BOUNDARY](sql-error-conditions-invalid-boundary.html)
 
+### INVALID_BITMAP_POSITION
+
+[SQLSTATE: 22003](sql-error-conditions-sqlstates.html#class-22-data-exception)
+
+The 0-indexed bitmap position `<bitPosition>` is out of bounds. The bitmap has 
`<bitmapNumBits>` bits (`<bitmapNumBytes>` bytes).
+
 ### INVALID_BUCKET_FILE
 
 SQLSTATE: none assigned


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to