You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maksim Zhuravkov (Jira)" <ji...@apache.org> on 2023/04/20 13:07:00 UTC
[jira] [Assigned] (IGNITE-18373) Sql, varbinary type erroneously processed.
[ https://issues.apache.org/jira/browse/IGNITE-18373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maksim Zhuravkov reassigned IGNITE-18373:
-----------------------------------------
Assignee: Maksim Zhuravkov
> Sql, varbinary type erroneously processed.
> --------------------------------------------
>
> Key: IGNITE-18373
> URL: https://issues.apache.org/jira/browse/IGNITE-18373
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 3.0.0-beta1
> Reporter: Evgeny Stanilovsky
> Assignee: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
>
> Check _test_blob_string.test_ignore_
> INSERT INTO blobs VALUES ('aaaaaaaaaa'::varbinary) erroneously parsed and obtain double casting from varbinary to binary(65535), starting point in
> TypeUtils#native2relationalType
> fast fix like near leads to green test, need further investigation.
> {code:java}
> case BYTES: {
> assert nativeType instanceof VarlenNativeType;
> var varlen = (VarlenNativeType) nativeType;
> return varlen.length() == Integer.MAX_VALUE ? factory.createSqlType(SqlTypeName.VARBINARY) : factory.createSqlType(SqlTypeName.VARBINARY, varlen.length());
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)