[jira] [Closed] (DRILL-4490) Count(*) function returns as optional instead of required
[
https://issues.apache.org/jira/browse/DRILL-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krystal closed DRILL-4490.
--
git.commit.id.abbrev=09b2627
Verified that bug is fixed.
create table test_tbl as select count(*) from abc;
schema of test_tbl:
message root {
required int64 EXPR$0;
}
> Count(*) function returns as optional instead of required
> -
>
> Key: DRILL-4490
> URL: https://issues.apache.org/jira/browse/DRILL-4490
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Data Types
>Affects Versions: 1.6.0
>Reporter: Krystal
>Assignee: Sean Hsuan-Yi Chu
> Fix For: 1.7.0
>
>
> git.commit.id.abbrev=c8a7840
> I have the following CTAS query:
> create table test as select count(*) as col1 from cp.`tpch/orders.parquet`;
> The schema of the test table shows col1 as optional:
> message root {
> optional int64 col1;
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DRILL-4127) HiveSchema.getSubSchema() should use lazy loading of all the table names
[ https://issues.apache.org/jira/browse/DRILL-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Challapalli updated DRILL-4127: - Reviewer: Dechang Gu (was: Rahul Challapalli) > HiveSchema.getSubSchema() should use lazy loading of all the table names > > > Key: DRILL-4127 > URL: https://issues.apache.org/jira/browse/DRILL-4127 > Project: Apache Drill > Issue Type: Bug >Reporter: Jinfeng Ni >Assignee: Jinfeng Ni > Fix For: 1.5.0 > > > Currently, HiveSchema.getSubSchema() will pre-load all the table names when > it constructs the subschema, even though those tables names are not requested > at all. This could cause considerably big performance overhead, especially > when the hive schema contains large # of objects (thousands of tables/views > are not un-common in some use case). > In stead, we should change the loading of table names to on-demand. Only when > there is a request of get all table names, we load them into hive schema. > This should help "show schemas", since it only requires the schema name, not > the table names in the schema. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (DRILL-4328) Fix for backward compatibility regression caused by DRILL-4198
[ https://issues.apache.org/jira/browse/DRILL-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Challapalli closed DRILL-4328. > Fix for backward compatibility regression caused by DRILL-4198 > -- > > Key: DRILL-4328 > URL: https://issues.apache.org/jira/browse/DRILL-4328 > Project: Apache Drill > Issue Type: Bug > Components: Storage - Other >Reporter: Venki Korukanti >Assignee: Venki Korukanti > Fix For: 1.5.0 > > > Revert updates made to StoragePlugin interface in DRILL-4198. Instead add the > new methods to AbstractStoragePlugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DRILL-4126) Adding HiveMetaStore caching when impersonation is enabled.
[ https://issues.apache.org/jira/browse/DRILL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Challapalli updated DRILL-4126: - Reviewer: Dechang Gu (was: Rahul Challapalli) > Adding HiveMetaStore caching when impersonation is enabled. > > > Key: DRILL-4126 > URL: https://issues.apache.org/jira/browse/DRILL-4126 > Project: Apache Drill > Issue Type: Bug >Reporter: Jinfeng Ni >Assignee: Jinfeng Ni > Fix For: 1.5.0 > > > Currently, HiveMetastore caching is used only when impersonation is disabled, > such that all the hivemetastore call goes through > NonCloseableHiveClientWithCaching [1]. However, if impersonation is enabled, > caching is not used for HiveMetastore access. > This could significantly increase the planning time when hive storage plugin > is enabled, or when running a query against INFORMATION_SCHEMA. Depending on > the # of databases/tables in Hive storage plugin, the planning time or > INFORMATION_SCHEMA query could become unacceptable. This becomes even worse > if the hive metastore is running on a different node from drillbit, making > the access of hivemetastore even slower. > We are seeing that it could takes 30~60 seconds for planning time, or > execution time for INFORMATION_SCHEMA query. The long planning or execution > time for INFORMATION_SCHEMA query prevents Drill from acting "interactively" > for such queries. > We should enable caching when impersonation is used. As long as the > authorizer verifies the user has the access to databases/tables, we should > get the data from caching. By doing that, we should see reduced number of api > call to HiveMetaStore. > [1] > https://github.com/apache/drill/blob/master/contrib/storage-hive/core/src/main/java/org/apache/drill/exec/store/hive/DrillHiveMetaStoreClient.java#L299 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (DRILL-4672) Browser !!!~~ 1 800 213 2171 Opera tech support telephone number
[ https://issues.apache.org/jira/browse/DRILL-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Takamori deleted DRILL-4672: --- > Browser !!!~~ 1 800 213 2171 Opera tech support telephone number > > > Key: DRILL-4672 > URL: https://issues.apache.org/jira/browse/DRILL-4672 > Project: Apache Drill > Issue Type: Bug >Reporter: ramjlal > > Browser !!!~~ 1 800 213 2171 Opera tech support telephone number > Describe Opera USA@1-800-213-2171 @tech support phone number Opera tech > support number, Opera customer support number,Opera support phone number USA > Canada UK Australia Opera customer service number, Opera customer service > phone number,Opera customer care number,Opera customer support number,Opera > tech support phone number, here. Opera UsA @ 1-800-213-2171 @ tech support > phone number Opera support phone number Describe Opera UsA @ 1-800-213-2171 @ > tech support phone number Opera support phone number here. Describe Opera Usa > @ 1-800-213-2171 @ tech support phone number Opera support phone number > here.Opera | 1-800-213-2171 | tech support phone number Opera customer care > phone number Opera support phone number 1-800-213-2171 (australia) Online > Best Opera support by toll free phone number 1-800-213-2171 (Australia) to > fix troubleshooting issues. We provide Opera technical customer service to > resolve problems when your printer not printing, problem to download printer > drivers, configure network and other issues. Keyword: Opera support, Opera > tech support phone number 1-800-213-2171(USA) Opera support phone number USA, > UK, CANADA,AustraliaOnline Best Opera support by toll free phone number > 1-800-213-2171 (Australia) to fix troubleshooting issues. We provide Opera > technical customer service to resolve problems when your printer not > printing, problem to download printer drivers, configure network and other > issues. (For UK 0-855-990-5999), (For USA 1-800-213-2171), (For AUSTRALIA > 1-800-213-2171) Opera service center number Opera customer service number usa > Opera telephone number Opera help number Opera customer service number usa > Opera service number Opera customer service telephone number Opera help > number Opera helpline number Opera tech support telephone number Operas > service center number Opera customer care number Opera support Canada phone > number Opera canada support number Opera phone number canada Opera canada > phone number Opera service center contact number Opera canada contact number > Opera contact number Canada Opera service toll free number Opera customer > care toll free number Opera customer support phone number Operas support > phone number Opera customer support phone number Opera support Opera support > number Opera usa support phone number Opera support phone number Opera > customer service number Opera technical support numberOpera help phone number > Opera support phone number Opera customer service number Opera technical > support number Opera help phone number Opera contact number Opera customer > service phone number usa Opera customer support number Operas tech support > phone number Opera phone number support phone number for Opera Opera tech > support number Operas phone number phone number for Operas Opera customer > care phone number Opera customer support telephone number Operas customer > service phone number Opera helpline phone number Opera support number usa > Opera 855 number Opera customer care phone number Opera technical support > telephone number Operas customer service number Operas customer care number > Opera printers contact number Dial @1-800-213-2171@ Opera driver support > number, Opera toll free number, Opera customer care toll free number, Opera > support toll free number, @1-800-213-2171@ Opera tech support, Opera tech > support number, Opera tech support phone number, Opera technical support, > Opera technical support number, Opera technical support phone number, > @1-800-213-2171 @ Opera Support phone number, Opera contact number, Opera > helpline number, Opera telephone number, contact number for Opera, telephone > number for Opera, @1-800-213-2171 @ Opera customer service number, Opera > Customer service phone number, Opera Customer support number, Opera printer > Customer support phone number, Opera Customer care number. Disclaimer: Opera > is an independent provider of remote tech support for third party products. > Any use of third party trademarks, brand names, product and services is only > referential. Opera hereby disclaims any sponsorship, affiliation or > endorsement of or by any third-parties. If your product is covered by > warranty, the support service > USA/Canada Wireless wi fi(((Unable to render embedded object: File (1 855 990 > 5999)))Opera
[jira] [Closed] (DRILL-4459) SchemaChangeException while querying hive json table
[
https://issues.apache.org/jira/browse/DRILL-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krystal closed DRILL-4459.
--
git.commit.id.abbrev=09b2627
Verified that bug is fixed.
> SchemaChangeException while querying hive json table
>
>
> Key: DRILL-4459
> URL: https://issues.apache.org/jira/browse/DRILL-4459
> Project: Apache Drill
> Issue Type: Bug
> Components: Functions - Drill, Functions - Hive
>Affects Versions: 1.4.0
> Environment: MapR-Drill 1.4.0
> Hive-1.2.0
>Reporter: Vitalii Diravka
>Assignee: Vitalii Diravka
> Fix For: 1.7.0
>
>
> getting the SchemaChangeException while querying json documents stored in
> hive table.
> {noformat}
> Error: SYSTEM ERROR: SchemaChangeException: Failure while trying to
> materialize incoming schema. Errors:
>
> Error in expression at index -1. Error: Missing function implementation:
> [castBIT(VAR16CHAR-OPTIONAL)]. Full expression: --UNKNOWN EXPRESSION--..
> {noformat}
> minimum reproduce
> {noformat}
> created sample json documents using the attached script(randomdata.sh)
> hive>create table simplejson(json string);
> hive>load data local inpath '/tmp/simple.json' into table simplejson;
> now query it through Drill.
> Drill Version
> select * from sys.version;
> +---++-+-++
> | commit_id | commit_message | commit_time | build_email | build_time |
> +---++-+-++
> | eafe0a245a0d4c0234bfbead10c6b2d7c8ef413d | DRILL-3901: Don't do early
> expansion of directory in the non-metadata-cache case because it already
> happens during ParquetGroupScan's metadata gathering operation. | 07.10.2015
> @ 17:12:57 UTC | Unknown | 07.10.2015 @ 17:36:16 UTC |
> +---++-+-++
> 0: jdbc:drill:zk=> select * from hive.`default`.simplejson where
> GET_JSON_OBJECT(simplejson.json, '$.DocId') = 'DocId2759947' limit 1;
> Error: SYSTEM ERROR: SchemaChangeException: Failure while trying to
> materialize incoming schema. Errors:
>
> Error in expression at index -1. Error: Missing function implementation:
> [castBIT(VAR16CHAR-OPTIONAL)]. Full expression: --UNKNOWN EXPRESSION--..
> Fragment 1:1
> [Error Id: 74f054a8-6f1d-4ddd-9064-3939fcc82647 on ip-10-0-0-233:31010]
> (state=,code=0)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DRILL-3584) Drill Kerberos HDFS Support / Documentation
[ https://issues.apache.org/jira/browse/DRILL-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15281835#comment-15281835 ] Santosh kulkarni commented on DRILL-3584: - As this ticket is still open, want to see if there are any new updates on Apache Drill with Kerberosized hadoop. If Nathan's blog is the resolution, will it work for all Hadoop distros? Didn't find any Kerberos information in Drill docs. > Drill Kerberos HDFS Support / Documentation > --- > > Key: DRILL-3584 > URL: https://issues.apache.org/jira/browse/DRILL-3584 > Project: Apache Drill > Issue Type: New Feature >Affects Versions: 1.1.0 >Reporter: Hari Sekhon >Assignee: Jacques Nadeau >Priority: Blocker > > I'm trying to find Drill docs for Kerberos support for secure HDFS clusters > and it doesn't appear to be well tested / supported / documented yet. > This product is Dead-on-Arrival if it doesn't integrate well with secure > Hadoop clusters, specifically HDFS + Kerberos (plus obviously secure > kerberized Hive/HCatalog etc.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DRILL-3510) Add ANSI_QUOTES option so that Drill's SQL Parser will recognize ANSI_SQL identifiers
[
https://issues.apache.org/jira/browse/DRILL-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15281658#comment-15281658
]
Charlie Frasure commented on DRILL-3510:
Agreed. I spent a long weekend trying to connect several commercial
products to 1.6 over both jdbc and odbc, most of which were unable to view
the "schemas" and "tables".
On Thu, May 12, 2016 at 11:35 AM, Andries Engelbrecht (JIRA) <
> Add ANSI_QUOTES option so that Drill's SQL Parser will recognize ANSI_SQL
> identifiers
> --
>
> Key: DRILL-3510
> URL: https://issues.apache.org/jira/browse/DRILL-3510
> Project: Apache Drill
> Issue Type: Improvement
> Components: SQL Parser
>Reporter: Jinfeng Ni
> Fix For: Future
>
> Attachments: DRILL-3510.patch, DRILL-3510.patch
>
>
> Currently Drill's SQL parser uses backtick as identifier quotes, the same as
> what MySQL does. However, this is different from ANSI SQL specification,
> where double quote is used as identifier quotes.
> MySQL has an option "ANSI_QUOTES", which could be switched on/off by user.
> Drill should follow the same way, so that Drill users do not have to rewrite
> their existing queries, if their queries use double quotes.
> {code}
> SET sql_mode='ANSI_QUOTES';
> {code}
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DRILL-786) Implement CROSS JOIN
[
https://issues.apache.org/jira/browse/DRILL-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15281633#comment-15281633
]
Andries Engelbrecht commented on DRILL-786:
---
Any movement on this?
Multiple tools (Tableau, MicroStrategy as examples) generate cross joins with
dimension tables when building dashboards/analytics.
> Implement CROSS JOIN
>
>
> Key: DRILL-786
> URL: https://issues.apache.org/jira/browse/DRILL-786
> Project: Apache Drill
> Issue Type: New Feature
> Components: Query Planning & Optimization
>Reporter: Krystal
> Fix For: Future
>
>
> git.commit.id.abbrev=5d7e3d3
> 0: jdbc:drill:schema=dfs> select student.name, student.age,
> student.studentnum from student cross join voter where student.age = 20 and
> voter.age = 20;
> Query failed: org.apache.drill.exec.rpc.RpcException: Remote failure while
> running query.[error_id: "af90e65a-c4d7-4635-a436-bbc1444c8db2"
> Root: rel#318:Subset#28.PHYSICAL.SINGLETON([]).[]
> Original rel:
> AbstractConverter(subset=[rel#318:Subset#28.PHYSICAL.SINGLETON([]).[]],
> convention=[PHYSICAL], DrillDistributionTraitDef=[SINGLETON([])], sort=[[]]):
> rowcount = 22500.0, cumulative cost = {inf}, id = 320
> DrillScreenRel(subset=[rel#317:Subset#28.LOGICAL.ANY([]).[]]): rowcount =
> 22500.0, cumulative cost = {2250.0 rows, 2250.0 cpu, 0.0 io, 0.0 network}, id
> = 316
> DrillProjectRel(subset=[rel#315:Subset#27.LOGICAL.ANY([]).[]], name=[$2],
> age=[$1], studentnum=[$3]): rowcount = 22500.0, cumulative cost = {22500.0
> rows, 12.0 cpu, 0.0 io, 0.0 network}, id = 314
> DrillJoinRel(subset=[rel#313:Subset#26.LOGICAL.ANY([]).[]],
> condition=[true], joinType=[inner]): rowcount = 22500.0, cumulative cost =
> {22500.0 rows, 0.0 cpu, 0.0 io, 0.0 network}, id = 312
> DrillFilterRel(subset=[rel#308:Subset#23.LOGICAL.ANY([]).[]],
> condition=[=(CAST($1):INTEGER, 20)]): rowcount = 150.0, cumulative cost =
> {1000.0 rows, 4000.0 cpu, 0.0 io, 0.0 network}, id = 307
> DrillScanRel(subset=[rel#306:Subset#22.LOGICAL.ANY([]).[]],
> table=[[dfs, student]]): rowcount = 1000.0, cumulative cost = {1000.0 rows,
> 4000.0 cpu, 0.0 io, 0.0 network}, id = 129
> DrillFilterRel(subset=[rel#311:Subset#25.LOGICAL.ANY([]).[]],
> condition=[=(CAST($1):INTEGER, 20)]): rowcount = 150.0, cumulative cost =
> {1000.0 rows, 4000.0 cpu, 0.0 io, 0.0 network}, id = 310
> DrillScanRel(subset=[rel#309:Subset#24.LOGICAL.ANY([]).[]],
> table=[[dfs, voter]]): rowcount = 1000.0, cumulative cost = {1000.0 rows,
> 2000.0 cpu, 0.0 io, 0.0 network}, id = 140
> Stack trace:
> org.eigenbase.relopt.RelOptPlanner$CannotPlanException: Node
> [rel#318:Subset#28.PHYSICAL.SINGLETON([]).[]] could not be implemented;
> planner state:
> Root: rel#318:Subset#28.PHYSICAL.SINGLETON([]).[]
> Original rel:
> AbstractConverter(subset=[rel#318:Subset#28.PHYSICAL.SINGLETON([]).[]],
> convention=[PHYSICAL], DrillDistributionTraitDef=[SINGLETON([])], sort=[[]]):
> rowcount = 22500.0, cumulative cost = {inf}, id = 320
> DrillScreenRel(subset=[rel#317:Subset#28.LOGICAL.ANY([]).[]]): rowcount =
> 22500.0, cumulative cost = {2250.0 rows, 2250.0 cpu, 0.0 io, 0.0 network}, id
> = 316
> DrillProjectRel(subset=[rel#315:Subset#27.LOGICAL.ANY([]).[]], name=[$2],
> age=[$1], studentnum=[$3]): rowcount = 22500.0, cumulative cost = {22500.0
> rows, 12.0 cpu, 0.0 io, 0.0 network}, id = 314
> DrillJoinRel(subset=[rel#313:Subset#26.LOGICAL.ANY([]).[]],
> condition=[true], joinType=[inner]): rowcount = 22500.0, cumulative cost =
> {22500.0 rows, 0.0 cpu, 0.0 io, 0.0 network}, id = 312
> DrillFilterRel(subset=[rel#308:Subset#23.LOGICAL.ANY([]).[]],
> condition=[=(CAST($1):INTEGER, 20)]): rowcount = 150.0, cumulative cost =
> {1000.0 rows, 4000.0 cpu, 0.0 io, 0.0 network}, id = 307
> DrillScanRel(subset=[rel#306:Subset#22.LOGICAL.ANY([]).[]],
> table=[[dfs, student]]): rowcount = 1000.0, cumulative cost = {1000.0 rows,
> 4000.0 cpu, 0.0 io, 0.0 network}, id = 129
> DrillFilterRel(subset=[rel#311:Subset#25.LOGICAL.ANY([]).[]],
> condition=[=(CAST($1):INTEGER, 20)]): rowcount = 150.0, cumulative cost =
> {1000.0 rows, 4000.0 cpu, 0.0 io, 0.0 network}, id = 310
> DrillScanRel(subset=[rel#309:Subset#24.LOGICAL.ANY([]).[]],
> table=[[dfs, voter]]): rowcount = 1000.0, cumulative cost = {1000.0 rows,
> 2000.0 cpu, 0.0 io, 0.0 network}, id = 140
> Sets:
> Set#22, type: (DrillRecordRow[*, age, name, studentnum])
> rel#306:Subset#22.LOGICAL.ANY([]).[], best=rel#129,
> importance=0.59049001
> rel#129:DrillScanRel.LOGICAL.ANY([]).[](table=[dfs, student]),
> rowcount=1000.0, cumulative cost={1000.0 rows, 4000.0 cpu, 0.0 io, 0.0
> network}
>
[jira] [Commented] (DRILL-3510) Add ANSI_QUOTES option so that Drill's SQL Parser will recognize ANSI_SQL identifiers
[
https://issues.apache.org/jira/browse/DRILL-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15281619#comment-15281619
]
Andries Engelbrecht commented on DRILL-3510:
What is the latest status on this?
We still see a lot of tool using double quotes, and many do not have the
ability to change the quote character or are cumbersome for users/partners.
> Add ANSI_QUOTES option so that Drill's SQL Parser will recognize ANSI_SQL
> identifiers
> --
>
> Key: DRILL-3510
> URL: https://issues.apache.org/jira/browse/DRILL-3510
> Project: Apache Drill
> Issue Type: Improvement
> Components: SQL Parser
>Reporter: Jinfeng Ni
> Fix For: Future
>
> Attachments: DRILL-3510.patch, DRILL-3510.patch
>
>
> Currently Drill's SQL parser uses backtick as identifier quotes, the same as
> what MySQL does. However, this is different from ANSI SQL specification,
> where double quote is used as identifier quotes.
> MySQL has an option "ANSI_QUOTES", which could be switched on/off by user.
> Drill should follow the same way, so that Drill users do not have to rewrite
> their existing queries, if their queries use double quotes.
> {code}
> SET sql_mode='ANSI_QUOTES';
> {code}
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DRILL-4673) Implement "DROP TABLE IF EXISTS" for drill to prevent FAILED status on command return
[ https://issues.apache.org/jira/browse/DRILL-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-4673: --- Description: Implement "DROP TABLE IF EXISTS" for drill to prevent FAILED status on command "DROP TABLE" return if table doesn't exist. was: Implement "DROP TABLE IF EXISTS" for drill to prevent FAILED status on command "DROP TABLE" return if table isn't exists. > Implement "DROP TABLE IF EXISTS" for drill to prevent FAILED status on > command return > - > > Key: DRILL-4673 > URL: https://issues.apache.org/jira/browse/DRILL-4673 > Project: Apache Drill > Issue Type: Bug > Components: Functions - Drill >Reporter: Vitalii Diravka >Assignee: Vitalii Diravka > Labels: drill > > Implement "DROP TABLE IF EXISTS" for drill to prevent FAILED status on > command "DROP TABLE" return if table doesn't exist. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DRILL-4673) Implement "DROP TABLE IF EXISTS" for drill to prevent FAILED status on command return
Vitalii Diravka created DRILL-4673: -- Summary: Implement "DROP TABLE IF EXISTS" for drill to prevent FAILED status on command return Key: DRILL-4673 URL: https://issues.apache.org/jira/browse/DRILL-4673 Project: Apache Drill Issue Type: Bug Components: Functions - Drill Reporter: Vitalii Diravka Assignee: Vitalii Diravka Implement "DROP TABLE IF EXISTS" for drill to prevent FAILED status on command "DROP TABLE" return if table isn't exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DRILL-4497) Casting strings with leading/trailing spaces to integers does not work
[
https://issues.apache.org/jira/browse/DRILL-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15281305#comment-15281305
]
Ian Hellstrom commented on DRILL-4497:
--
This behaviour is the same as in Java and is likely a consequence of it.
> Casting strings with leading/trailing spaces to integers does not work
> --
>
> Key: DRILL-4497
> URL: https://issues.apache.org/jira/browse/DRILL-4497
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.5.0
>Reporter: Ian Hellstrom
>
> When casting a string with leading and/or trailing spaces to an integer type
> (e.g. INT or BIGINT), an exception is thrown. Casting the same numbers to
> floating-point numbers works.
> This is inconsistent and extremely confusing. Simply using TRIM() before
> casting works though.
> {code}
> SELECT CAST(' 1' AS INT) FROM ...
> SELECT CAST('1 ' AS INT) FROM ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
