[jira] [Updated] (SPARK-20382) fileSystem.closed when run load data on spark beeline
[ https://issues.apache.org/jira/browse/SPARK-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] QQShu1 updated SPARK-20382: --- Summary: fileSystem.closed when run load data on spark beeline (was: fileSystem.closed when run load data on beeline) > fileSystem.closed when run load data on spark beeline > --- > > Key: SPARK-20382 > URL: https://issues.apache.org/jira/browse/SPARK-20382 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: QQShu1 > > we run on beeline steps as follows: > 1. hadoop fs -put kv1.txt hdfs://spark/user/ > 2.Connect beeline > 3. LOAD DATA INPATH 'hdfs://spark/user/kv1.txt' INTO TABLE src_txt16; > 4.exit beeline > 5.Connect beeline > 6.hadoop fs -put kv1.txt hdfs://spark/user/ > 7.run the LOAD DATA command again , we will meet fileSystem.closed error -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-20382) fileSystem.closed when run load data on beeline
[ https://issues.apache.org/jira/browse/SPARK-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974183#comment-15974183 ] QQShu1 commented on SPARK-20382: @Umesh Chaudhary this beeline is spark beeline, not the hive . > fileSystem.closed when run load data on beeline > - > > Key: SPARK-20382 > URL: https://issues.apache.org/jira/browse/SPARK-20382 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: QQShu1 > > we run on beeline steps as follows: > 1. hadoop fs -put kv1.txt hdfs://spark/user/ > 2.Connect beeline > 3. LOAD DATA INPATH 'hdfs://spark/user/kv1.txt' INTO TABLE src_txt16; > 4.exit beeline > 5.Connect beeline > 6.hadoop fs -put kv1.txt hdfs://spark/user/ > 7.run the LOAD DATA command again , we will meet fileSystem.closed error -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-20382) fileSystem.closed when we run load data on beeline
[ https://issues.apache.org/jira/browse/SPARK-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] QQShu1 updated SPARK-20382: --- Summary: fileSystem.closed when we run load data on beeline (was: we meet fileSystem.closed when we run load data on beeline) > fileSystem.closed when we run load data on beeline > --- > > Key: SPARK-20382 > URL: https://issues.apache.org/jira/browse/SPARK-20382 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: QQShu1 > > we run on beeline steps as follows: > 1. hadoop fs -put kv1.txt hdfs://spark/user/ > 2.Connect beeline > 3. LOAD DATA INPATH 'hdfs://spark/user/kv1.txt' INTO TABLE src_txt16; > 4.exit beeline > 5.Connect beeline > 6.hadoop fs -put kv1.txt hdfs://spark/user/ > 7.run the LOAD DATA command again , we will meet fileSystem.closed error -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-20382) fileSystem.closed when run load data on beeline
[ https://issues.apache.org/jira/browse/SPARK-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] QQShu1 updated SPARK-20382: --- Summary: fileSystem.closed when run load data on beeline (was: fileSystem.closed when we run load data on beeline) > fileSystem.closed when run load data on beeline > - > > Key: SPARK-20382 > URL: https://issues.apache.org/jira/browse/SPARK-20382 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: QQShu1 > > we run on beeline steps as follows: > 1. hadoop fs -put kv1.txt hdfs://spark/user/ > 2.Connect beeline > 3. LOAD DATA INPATH 'hdfs://spark/user/kv1.txt' INTO TABLE src_txt16; > 4.exit beeline > 5.Connect beeline > 6.hadoop fs -put kv1.txt hdfs://spark/user/ > 7.run the LOAD DATA command again , we will meet fileSystem.closed error -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Comment Edited] (SPARK-20382) we meet fileSystem.closed when we run load data on beeline
[ https://issues.apache.org/jira/browse/SPARK-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974022#comment-15974022 ] QQShu1 edited comment on SPARK-20382 at 4/19/17 3:58 AM: - I find in Hive.java needToCopy HadoopShims.HdfsEncryptionShim srcHdfsEncryptionShim = SessionState.get().getHdfsEncryptionShim(srcFs); in SessionState has a map hdfsEncryptionShims,in HdfsEncryptionShim has a HdfsAdmin, and when we exit beeline ,we call HiveSessionImplwithUGI that FileSystem.closeAllForUGI(sessionUgi). and the fileSystem in HdfsAdmin will be close. Because beeline use one org.apache.hadoop.hive.ql.session.SessionState， so the next beeline will get the same object of HdfsAdmin,and in srcHdfsEncryptionShim.isPathEncrypted(srcf), will call the DFSClient.checkOpen, that throw the ava.io.IOException: Filesystem closed. was (Author: qqshu11): I find in Hive.java needToCopy HadoopShims.HdfsEncryptionShim srcHdfsEncryptionShim = SessionState.get().getHdfsEncryptionShim(srcFs); in SessionState has a map hdfsEncryptionShims,in HdfsEncryptionShim has a HdfsAdmin, and when we ext beeline ,we call HiveSessionImplwithUGI that FileSystem.closeAllForUGI(sessionUgi). and the fileSystem in HdfsAdmin will be close. Beacure beeline use one org.apache.hadoop.hive.ql.session.SessionState， so the next beeline will get the same object of HdfsAdmin,and in srcHdfsEncryptionShim.isPathEncrypted(srcf), will call the DFSClient.checkOpen, that throw the ava.io.IOException: Filesystem closed. > we meet fileSystem.closed when we run load data on beeline > -- > > Key: SPARK-20382 > URL: https://issues.apache.org/jira/browse/SPARK-20382 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: QQShu1 > > we run on beeline steps as follows: > 1. hadoop fs -put kv1.txt hdfs://spark/user/ > 2.Connect beeline > 3. LOAD DATA INPATH 'hdfs://spark/user/kv1.txt' INTO TABLE src_txt16; > 4.exit beeline > 5.Connect beeline > 6.hadoop fs -put kv1.txt hdfs://spark/user/ > 7.run the LOAD DATA command again , we will meet fileSystem.closed error -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-20382) we meet fileSystem.closed when we run load data on beeline
[ https://issues.apache.org/jira/browse/SPARK-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974022#comment-15974022 ] QQShu1 commented on SPARK-20382: I find in Hive.java needToCopy HadoopShims.HdfsEncryptionShim srcHdfsEncryptionShim = SessionState.get().getHdfsEncryptionShim(srcFs); in SessionState has a map hdfsEncryptionShims,in HdfsEncryptionShim has a HdfsAdmin, and when we ext beeline ,we call HiveSessionImplwithUGI that FileSystem.closeAllForUGI(sessionUgi). and the fileSystem in HdfsAdmin will be close. Beacure beeline use one org.apache.hadoop.hive.ql.session.SessionState， so the next beeline will get the same object of HdfsAdmin,and in srcHdfsEncryptionShim.isPathEncrypted(srcf), will call the DFSClient.checkOpen, that throw the ava.io.IOException: Filesystem closed. > we meet fileSystem.closed when we run load data on beeline > -- > > Key: SPARK-20382 > URL: https://issues.apache.org/jira/browse/SPARK-20382 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: QQShu1 > > we run on beeline steps as follows: > 1. hadoop fs -put kv1.txt hdfs://spark/user/ > 2.Connect beeline > 3. LOAD DATA INPATH 'hdfs://spark/user/kv1.txt' INTO TABLE src_txt16; > 4.exit beeline > 5.Connect beeline > 6.hadoop fs -put kv1.txt hdfs://spark/user/ > 7.run the LOAD DATA command again , we will meet fileSystem.closed error -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Closed] (SPARK-20363) sessionstate.get is get the same object in hive project, when I use spark-beeline
[ https://issues.apache.org/jira/browse/SPARK-20363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] QQShu1 closed SPARK-20363. -- > sessionstate.get is get the same object in hive project, when I use > spark-beeline > -- > > Key: SPARK-20363 > URL: https://issues.apache.org/jira/browse/SPARK-20363 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.2 >Reporter: QQShu1 > > sessionstate.get is get the same object in hive project, when I use > spark-beeline,but when I use hive beeline,sessionstate.get is get the > different object in hive project -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Created] (SPARK-20382) we meet fileSystem.closed when we run load data on beeline
QQShu1 created SPARK-20382: -- Summary: we meet fileSystem.closed when we run load data on beeline Key: SPARK-20382 URL: https://issues.apache.org/jira/browse/SPARK-20382 Project: Spark Issue Type: Bug Components: SQL Affects Versions: 2.1.0 Reporter: QQShu1 we run on beeline steps as follows: 1. hadoop fs -put kv1.txt hdfs://spark/user/ 2.Connect beeline 3. LOAD DATA INPATH 'hdfs://spark/user/kv1.txt' INTO TABLE src_txt16; 4.exit beeline 5.Connect beeline 6.hadoop fs -put kv1.txt hdfs://spark/user/ 7.run the LOAD DATA command again , we will meet fileSystem.closed error -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Created] (SPARK-20363) sessionstate.get is get the same object in hive project, when I use spark-beeline
QQShu1 created SPARK-20363: -- Summary: sessionstate.get is get the same object in hive project, when I use spark-beeline Key: SPARK-20363 URL: https://issues.apache.org/jira/browse/SPARK-20363 Project: Spark Issue Type: Bug Components: SQL Affects Versions: 2.1.2 Reporter: QQShu1 sessionstate.get is get the same object in hive project, when I use spark-beeline,but when I use hive beeline,sessionstate.get is get the different object in hive project -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Closed] (SPARK-20118) spark2.1 support numeric datatype
[ https://issues.apache.org/jira/browse/SPARK-20118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] QQShu1 closed SPARK-20118. -- > spark2.1 support numeric datatype > - > > Key: SPARK-20118 > URL: https://issues.apache.org/jira/browse/SPARK-20118 > Project: Spark > Issue Type: New Feature > Components: SQL >Affects Versions: 2.1.0 >Reporter: QQShu1 > > spark2.1 now don`t support numeric. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Created] (SPARK-20118) spark2.1 support numeric datatype
QQShu1 created SPARK-20118: -- Summary: spark2.1 support numeric datatype Key: SPARK-20118 URL: https://issues.apache.org/jira/browse/SPARK-20118 Project: Spark Issue Type: New Feature Components: SQL Affects Versions: 2.1.0 Reporter: QQShu1 spark2.1 now don`t support numeric. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-20068) Twenty-two column coalesce has pool performance when codegen is open
[ https://issues.apache.org/jira/browse/SPARK-20068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15939820#comment-15939820 ] QQShu1 commented on SPARK-20068: @Takeshi Yamamuro thanks for your answer. V2.1 doesn`t have this issue. > Twenty-two column coalesce has pool performance when codegen is open > > > Key: SPARK-20068 > URL: https://issues.apache.org/jira/browse/SPARK-20068 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.5.0 >Reporter: QQShu1 > > when the coalesce has Twenty-one column the select performance is well, but > the Twenty-two column coalesce the select performance is pool. > I use the 22 column coalesce select commend is that : > SELECT > SUM(COALESCE(col1,0)) AS CUSTOM1, > SUM(COALESCE(col2,0)) AS CUSTOM2, > SUM(COALESCE(col3,0)) AS CUSTOM3, > SUM(COALESCE(col4,0)) AS CUSTOM4, > SUM(COALESCE(col5,0)) AS CUSTOM5, > SUM(COALESCE(col6,0)) AS CUSTOM6, > SUM(COALESCE(col7,0)) AS CUSTOM7, > SUM(COALESCE(col8,0)) AS CUSTOM8, > SUM(COALESCE(col9,0)) AS CUSTOM9, > SUM(COALESCE(col10,0)) AS CUSTOM10, > SUM(COALESCE(col11,0)) AS CUSTOM11, > SUM(COALESCE(col12,0)) AS CUSTOM12, > SUM(COALESCE(col13,0)) AS CUSTOM13, > SUM(COALESCE(col14,0)) AS CUSTOM14, > SUM(COALESCE(col15,0)) AS CUSTOM15, > SUM(COALESCE(col16,0)) AS CUSTOM16, > SUM(COALESCE(col17,0)) AS CUSTOM17, > SUM(COALESCE(col18,0)) AS CUSTOM18, > SUM(COALESCE(col19,0)) AS CUSTOM19, > SUM(COALESCE(col20,0)) AS CUSTOM20, > SUM(COALESCE(col21,0)) AS CUSTOM21, > SUM(COALESCE(col22,0)) AS CUSTOM22 > FROM txt_table ; > the 21 column select commend it that: > SELECT > SUM(COALESCE(col1,0)) AS CUSTOM1, > SUM(COALESCE(col2,0)) AS CUSTOM2, > SUM(COALESCE(col3,0)) AS CUSTOM3, > SUM(COALESCE(col4,0)) AS CUSTOM4, > SUM(COALESCE(col5,0)) AS CUSTOM5, > SUM(COALESCE(col6,0)) AS CUSTOM6, > SUM(COALESCE(col7,0)) AS CUSTOM7, > SUM(COALESCE(col8,0)) AS CUSTOM8, > SUM(COALESCE(col9,0)) AS CUSTOM9, > SUM(COALESCE(col10,0)) AS CUSTOM10, > SUM(COALESCE(col11,0)) AS CUSTOM11, > SUM(COALESCE(col12,0)) AS CUSTOM12, > SUM(COALESCE(col13,0)) AS CUSTOM13, > SUM(COALESCE(col14,0)) AS CUSTOM14, > SUM(COALESCE(col15,0)) AS CUSTOM15, > SUM(COALESCE(col16,0)) AS CUSTOM16, > SUM(COALESCE(col17,0)) AS CUSTOM17, > SUM(COALESCE(col18,0)) AS CUSTOM18, > SUM(COALESCE(col19,0)) AS CUSTOM19, > SUM(COALESCE(col20,0)) AS CUSTOM20, > SUM(COALESCE(col21,0)) AS CUSTOM21 > FROM txt_table ; -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-20068) Twenty-two column coalesce has pool performance when codegen is open
[ https://issues.apache.org/jira/browse/SPARK-20068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937931#comment-15937931 ] QQShu1 commented on SPARK-20068: @Sean Owen thanks for your answer.But if I remove the coalesce of all, the 22 coalesce select performance is well.and if I close the codegen ,the difference between 21 coalesce and 22 coalesce will disappear. > Twenty-two column coalesce has pool performance when codegen is open > > > Key: SPARK-20068 > URL: https://issues.apache.org/jira/browse/SPARK-20068 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.5.0 >Reporter: QQShu1 > > when the coalesce has Twenty-one column the select performance is well, but > the Twenty-two column coalesce the select performance is pool. > I use the 22 column coalesce select commend is that : > SELECT > SUM(COALESCE(col1,0)) AS CUSTOM1, > SUM(COALESCE(col2,0)) AS CUSTOM2, > SUM(COALESCE(col3,0)) AS CUSTOM3, > SUM(COALESCE(col4,0)) AS CUSTOM4, > SUM(COALESCE(col5,0)) AS CUSTOM5, > SUM(COALESCE(col6,0)) AS CUSTOM6, > SUM(COALESCE(col7,0)) AS CUSTOM7, > SUM(COALESCE(col8,0)) AS CUSTOM8, > SUM(COALESCE(col9,0)) AS CUSTOM9, > SUM(COALESCE(col10,0)) AS CUSTOM10, > SUM(COALESCE(col11,0)) AS CUSTOM11, > SUM(COALESCE(col12,0)) AS CUSTOM12, > SUM(COALESCE(col13,0)) AS CUSTOM13, > SUM(COALESCE(col14,0)) AS CUSTOM14, > SUM(COALESCE(col15,0)) AS CUSTOM15, > SUM(COALESCE(col16,0)) AS CUSTOM16, > SUM(COALESCE(col17,0)) AS CUSTOM17, > SUM(COALESCE(col18,0)) AS CUSTOM18, > SUM(COALESCE(col19,0)) AS CUSTOM19, > SUM(COALESCE(col20,0)) AS CUSTOM20, > SUM(COALESCE(col21,0)) AS CUSTOM21, > SUM(COALESCE(col22,0)) AS CUSTOM22 > FROM txt_table ; > the 21 column select commend it that: > SELECT > SUM(COALESCE(col1,0)) AS CUSTOM1, > SUM(COALESCE(col2,0)) AS CUSTOM2, > SUM(COALESCE(col3,0)) AS CUSTOM3, > SUM(COALESCE(col4,0)) AS CUSTOM4, > SUM(COALESCE(col5,0)) AS CUSTOM5, > SUM(COALESCE(col6,0)) AS CUSTOM6, > SUM(COALESCE(col7,0)) AS CUSTOM7, > SUM(COALESCE(col8,0)) AS CUSTOM8, > SUM(COALESCE(col9,0)) AS CUSTOM9, > SUM(COALESCE(col10,0)) AS CUSTOM10, > SUM(COALESCE(col11,0)) AS CUSTOM11, > SUM(COALESCE(col12,0)) AS CUSTOM12, > SUM(COALESCE(col13,0)) AS CUSTOM13, > SUM(COALESCE(col14,0)) AS CUSTOM14, > SUM(COALESCE(col15,0)) AS CUSTOM15, > SUM(COALESCE(col16,0)) AS CUSTOM16, > SUM(COALESCE(col17,0)) AS CUSTOM17, > SUM(COALESCE(col18,0)) AS CUSTOM18, > SUM(COALESCE(col19,0)) AS CUSTOM19, > SUM(COALESCE(col20,0)) AS CUSTOM20, > SUM(COALESCE(col21,0)) AS CUSTOM21 > FROM txt_table ; -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Created] (SPARK-20068) Twenty-two column coalesce has pool performance when codegen is open
QQShu1 created SPARK-20068: -- Summary: Twenty-two column coalesce has pool performance when codegen is open Key: SPARK-20068 URL: https://issues.apache.org/jira/browse/SPARK-20068 Project: Spark Issue Type: Bug Components: SQL Affects Versions: 1.5.0 Reporter: QQShu1 when the coalesce has Twenty-one column the select performance is well, but the Twenty-two column coalesce the select performance is pool. I use the 22 column coalesce select commend is that : SELECT SUM(COALESCE(col1,0)) AS CUSTOM1, SUM(COALESCE(col2,0)) AS CUSTOM2, SUM(COALESCE(col3,0)) AS CUSTOM3, SUM(COALESCE(col4,0)) AS CUSTOM4, SUM(COALESCE(col5,0)) AS CUSTOM5, SUM(COALESCE(col6,0)) AS CUSTOM6, SUM(COALESCE(col7,0)) AS CUSTOM7, SUM(COALESCE(col8,0)) AS CUSTOM8, SUM(COALESCE(col9,0)) AS CUSTOM9, SUM(COALESCE(col10,0)) AS CUSTOM10, SUM(COALESCE(col11,0)) AS CUSTOM11, SUM(COALESCE(col12,0)) AS CUSTOM12, SUM(COALESCE(col13,0)) AS CUSTOM13, SUM(COALESCE(col14,0)) AS CUSTOM14, SUM(COALESCE(col15,0)) AS CUSTOM15, SUM(COALESCE(col16,0)) AS CUSTOM16, SUM(COALESCE(col17,0)) AS CUSTOM17, SUM(COALESCE(col18,0)) AS CUSTOM18, SUM(COALESCE(col19,0)) AS CUSTOM19, SUM(COALESCE(col20,0)) AS CUSTOM20, SUM(COALESCE(col21,0)) AS CUSTOM21, SUM(COALESCE(col22,0)) AS CUSTOM22 FROM txt_table ; the 21 column select commend it that: SELECT SUM(COALESCE(col1,0)) AS CUSTOM1, SUM(COALESCE(col2,0)) AS CUSTOM2, SUM(COALESCE(col3,0)) AS CUSTOM3, SUM(COALESCE(col4,0)) AS CUSTOM4, SUM(COALESCE(col5,0)) AS CUSTOM5, SUM(COALESCE(col6,0)) AS CUSTOM6, SUM(COALESCE(col7,0)) AS CUSTOM7, SUM(COALESCE(col8,0)) AS CUSTOM8, SUM(COALESCE(col9,0)) AS CUSTOM9, SUM(COALESCE(col10,0)) AS CUSTOM10, SUM(COALESCE(col11,0)) AS CUSTOM11, SUM(COALESCE(col12,0)) AS CUSTOM12, SUM(COALESCE(col13,0)) AS CUSTOM13, SUM(COALESCE(col14,0)) AS CUSTOM14, SUM(COALESCE(col15,0)) AS CUSTOM15, SUM(COALESCE(col16,0)) AS CUSTOM16, SUM(COALESCE(col17,0)) AS CUSTOM17, SUM(COALESCE(col18,0)) AS CUSTOM18, SUM(COALESCE(col19,0)) AS CUSTOM19, SUM(COALESCE(col20,0)) AS CUSTOM20, SUM(COALESCE(col21,0)) AS CUSTOM21 FROM txt_table ; -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
