This is an automated email from the ASF dual-hosted git repository.
abhishek pushed a commit to branch 29.0.0
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/29.0.0 by this push:
new 9f300e4b183 Fix up typo </br /> -> <br /> and adjust interpolated
exception msg in InvalidNullByteFault. (#15804) (#15808)
9f300e4b183 is described below
commit 9f300e4b18369e15b0674c0cdee0d0e89528226f
Author: Laksh Singla <[email protected]>
AuthorDate: Wed Jan 31 14:30:29 2024 +0530
Fix up typo </br /> -> <br /> and adjust interpolated exception msg in
InvalidNullByteFault. (#15804) (#15808)
Co-authored-by: Abhishek Radhakrishnan <[email protected]>
---
docs/multi-stage-query/reference.md | 2 +-
.../java/org/apache/druid/msq/indexing/error/InvalidNullByteFault.java | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/multi-stage-query/reference.md
b/docs/multi-stage-query/reference.md
index db003a68304..1087c1564fd 100644
--- a/docs/multi-stage-query/reference.md
+++ b/docs/multi-stage-query/reference.md
@@ -433,7 +433,7 @@ The following table describes error codes you may encounter
in the `multiStageQu
| <a name="error_InsertLockPreempted">`InsertLockPreempted`</a> | An INSERT or
REPLACE query was canceled by a higher-priority ingestion job, such as a
real-time ingestion task. | |
| <a name="error_InsertTimeNull">`InsertTimeNull`</a> | An INSERT or REPLACE
query encountered a null timestamp in the `__time` field.<br /><br />This can
happen due to using an expression like `TIME_PARSE(timestamp) AS __time` with a
timestamp that cannot be parsed.
([`TIME_PARSE`](../querying/sql-scalar.md#date-and-time-functions) returns null
when it cannot parse a timestamp.) In this case, try parsing your timestamps
using a different function or pattern. Or, if your timestamps may g [...]
| <a name="error_InsertTimeOutOfBounds">`InsertTimeOutOfBounds`</a> | A
REPLACE query generated a timestamp outside the bounds of the TIMESTAMP
parameter for your OVERWRITE WHERE clause.<br /> <br />To avoid this error,
verify that the you specified is valid. | `interval`: time chunk interval
corresponding to the out-of-bounds timestamp |
-| <a name="error_InvalidNullByte">`InvalidNullByte`</a> | A string column
included a null byte. Null bytes in strings are not permitted. |`source`: The
source that included the null byte <br /></br /> `rowNumber`: The row number
(1-indexed) that included the null byte <br /><br /> `column`: The column that
included the null byte <br /><br /> `value`: Actual string containing the null
byte <br /><br /> `position`: Position (1-indexed) of occurrence of null byte|
+| <a name="error_InvalidNullByte">`InvalidNullByte`</a> | A string column
included a null byte. Null bytes in strings are not permitted. |`source`: The
source that included the null byte <br /><br /> `rowNumber`: The row number
(1-indexed) that included the null byte <br /><br /> `column`: The column that
included the null byte <br /><br /> `value`: Actual string containing the null
byte <br /><br /> `position`: Position (1-indexed) of occurrence of null byte|
| <a name="error_QueryNotSupported">`QueryNotSupported`</a> | QueryKit could
not translate the provided native query to a multi-stage query.<br /> <br
/>This can happen if the query uses features that aren't supported, like
GROUPING SETS. | |
| <a name="error_QueryRuntimeError">`QueryRuntimeError`</a> | MSQ uses the
native query engine to run the leaf stages. This error tells MSQ that error is
in native query runtime.<br /> <br /> Since this is a generic error, the user
needs to look at logs for the error message and stack trace to figure out the
next course of action. If the user is stuck, consider raising a `github` issue
for assistance. | `baseErrorMessage` error message from the native query
runtime. |
| <a name="error_RowTooLarge">`RowTooLarge`</a> | The query tried to process a
row that was too large to write to a single frame. See the [Limits](#limits)
table for specific limits on frame size. Note that the effective maximum row
size is smaller than the maximum frame size due to alignment considerations
during frame writing. | `maxFrameSize`: The limit on the frame size. |
diff --git
a/extensions-core/multi-stage-query/src/main/java/org/apache/druid/msq/indexing/error/InvalidNullByteFault.java
b/extensions-core/multi-stage-query/src/main/java/org/apache/druid/msq/indexing/error/InvalidNullByteFault.java
index 0e85e6817d4..e66f8cc80c5 100644
---
a/extensions-core/multi-stage-query/src/main/java/org/apache/druid/msq/indexing/error/InvalidNullByteFault.java
+++
b/extensions-core/multi-stage-query/src/main/java/org/apache/druid/msq/indexing/error/InvalidNullByteFault.java
@@ -63,7 +63,7 @@ public class InvalidNullByteFault extends BaseMSQFault
{
super(
CODE,
- "Invalid null byte at source [%s], rowNumber [%d], column[%s],
value[%s], position[%d]. "
+ "Invalid null byte at source[%s], rowNumber[%d], column[%s],
value[%s], position[%d]. "
+ "Consider sanitizing the input string column using REPLACE(\"%s\",
U&'\\0000', '') AS %s",
source,
rowNumber,
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
