[jira] [Resolved] (LIVY-987) NPE when waiting for thrift session to start timeout.

[ https://issues.apache.org/jira/browse/LIVY-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido resolved LIVY-987. -- Resolution: Fixed Issue resolved by https://github.com/apache/incubator-livy/pull/416. > NPE when

[jira] [Updated] (LIVY-987) NPE when waiting for thrift session to start timeout.

[ https://issues.apache.org/jira/browse/LIVY-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido updated LIVY-987: - Fix Version/s: 0.9.0 > NPE when waiting for thrift session to start timeout. >

[jira] [Updated] (LIVY-987) NPE when waiting for thrift session to start timeout.

[ https://issues.apache.org/jira/browse/LIVY-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido updated LIVY-987: - Component/s: Thriftserver > NPE when waiting for thrift session to start timeout. >

[jira] [Comment Edited] (SPARK-14516) Clustering evaluator

[ https://issues.apache.org/jira/browse/SPARK-14516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16069815#comment-16069815 ] Marco Gaido edited comment on SPARK-14516 at 3/27/23 9:42 AM: -- Hello

[jira] [Commented] (SPARK-14516) Clustering evaluator

[ https://issues.apache.org/jira/browse/SPARK-14516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705265#comment-17705265 ] Marco Gaido commented on SPARK-14516: - As there are some issues with the Google Doc sharing, I

[jira] [Commented] (LIVY-899) The state of interactive session is always idle when using thrift protocol.

[ https://issues.apache.org/jira/browse/LIVY-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634337#comment-17634337 ] Marco Gaido commented on LIVY-899: -- Can you reproduce the issue with a UT? If so, please  create a PR with

[jira] [Assigned] (LIVY-899) The state of interactive session is always idle when using thrift protocol.

[ https://issues.apache.org/jira/browse/LIVY-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-899: Assignee: (was: Marco Gaido) > The state of interactive session is always idle when using

[jira] [Commented] (SPARK-36673) Incorrect Unions of struct with mismatched field name case

[ https://issues.apache.org/jira/browse/SPARK-36673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17410488#comment-17410488 ] Marco Gaido commented on SPARK-36673: - AFAIK, in SQL the names in the struct are case sensitive,

[jira] [Resolved] (LIVY-754) precision and scale are not encoded in decimal type

[ https://issues.apache.org/jira/browse/LIVY-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido resolved LIVY-754. -- Fix Version/s: 0.8.0 Assignee: Wing Yew Poon Resolution: Fixed Issue resolved by PR: 

[jira] [Resolved] (LIVY-752) Livy TS does not accept any connections when limits are set on connections

[ https://issues.apache.org/jira/browse/LIVY-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido resolved LIVY-752. -- Fix Version/s: 0.8.0 Assignee: Wing Yew Poon Resolution: Fixed Issue resolved by PR: 

[jira] [Resolved] (LIVY-745) more than 11 concurrent clients lead to java.io.IOException: Unable to connect to provided ports 10000~10010

[ https://issues.apache.org/jira/browse/LIVY-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido resolved LIVY-745. -- Fix Version/s: 0.7.0 Assignee: Wing Yew Poon Resolution: Fixed Issue resolved by pull

[jira] [Comment Edited] (LIVY-718) Support multi-active high availability in Livy

[ https://issues.apache.org/jira/browse/LIVY-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17005512#comment-17005512 ] Marco Gaido edited comment on LIVY-718 at 12/30/19 6:29 PM: bq. IIRC JDBC had a

[jira] [Commented] (LIVY-718) Support multi-active high availability in Livy

[ https://issues.apache.org/jira/browse/LIVY-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17005512#comment-17005512 ] Marco Gaido commented on LIVY-718: -- > IIRC JDBC had a REST and an RPC mode. The RPC mode might not be HA

[jira] [Commented] (LIVY-718) Support multi-active high availability in Livy

[ https://issues.apache.org/jira/browse/LIVY-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17005063#comment-17005063 ] Marco Gaido commented on LIVY-718: -- Thanks for your comments [~bikassaha]. I am not sure (actually I think

[jira] [Commented] (SPARK-29667) implicitly convert mismatched datatypes on right side of "IN" operator

[ https://issues.apache.org/jira/browse/SPARK-29667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987712#comment-16987712 ] Marco Gaido commented on SPARK-29667: - I can agree more with you [~hyukjin.kwon]. I think that

[jira] [Assigned] (LIVY-705) Support getting keystore password from Hadoop credential provider for Thrift server

[ https://issues.apache.org/jira/browse/LIVY-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-705: Assignee: Wing Yew Poon > Support getting keystore password from Hadoop credential provider for

[jira] [Resolved] (LIVY-705) Support getting keystore password from Hadoop credential provider for Thrift server

[ https://issues.apache.org/jira/browse/LIVY-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido resolved LIVY-705. -- Fix Version/s: 0.7.0 Resolution: Fixed Issue resolved by PR

[jira] [Resolved] (LIVY-356) Add support for LDAP authentication in Livy Server

[ https://issues.apache.org/jira/browse/LIVY-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido resolved LIVY-356. -- Fix Version/s: 0.7.0 Assignee: mingchao zhao Resolution: Fixed Issue resolved by

[jira] [Commented] (LIVY-667) Support query a lot of data.

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935852#comment-16935852 ] Marco Gaido commented on LIVY-667: -- [~yihengw] yes, that's true. The point is that the data needs to be

[jira] [Commented] (LIVY-667) Support query a lot of data.

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935616#comment-16935616 ] Marco Gaido commented on LIVY-667: -- [~runzhiwang] let me cite you in the JIRA body: > When enable

[jira] [Resolved] (LIVY-683) Livy SQLInterpreter get empty array when extract date format rows to json

[ https://issues.apache.org/jira/browse/LIVY-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido resolved LIVY-683. -- Resolution: Duplicate > Livy SQLInterpreter get empty array when extract date format rows to json >

[jira] [Assigned] (LIVY-683) Livy SQLInterpreter get empty array when extract date format rows to json

[ https://issues.apache.org/jira/browse/LIVY-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-683: Assignee: (was: Zhefeng Wang) > Livy SQLInterpreter get empty array when extract date format

[jira] [Commented] (LIVY-667) Support query a lot of data.

[ https://issues.apache.org/jira/browse/LIVY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16934489#comment-16934489 ] Marco Gaido commented on LIVY-667: -- [~runzhiwang] I'd argue that if the data which is present in a single

[jira] [Commented] (SPARK-29123) DecimalType multiplication precision loss

[ https://issues.apache.org/jira/browse/SPARK-29123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933560#comment-16933560 ] Marco Gaido commented on SPARK-29123: - [~benny] the point here is: Spark can represent decimals with

[jira] [Commented] (SPARK-29123) DecimalType multiplication precision loss

[ https://issues.apache.org/jira/browse/SPARK-29123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16933128#comment-16933128 ] Marco Gaido commented on SPARK-29123: - You can set

[jira] [Commented] (SPARK-29038) SPIP: Support Spark Materialized View

[ https://issues.apache.org/jira/browse/SPARK-29038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926650#comment-16926650 ] Marco Gaido commented on SPARK-29038: - [~cltlfcjin] currently spark has a something similar, which

[jira] [Comment Edited] (SPARK-29038) SPIP: Support Spark Materialized View

[ https://issues.apache.org/jira/browse/SPARK-29038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926650#comment-16926650 ] Marco Gaido edited comment on SPARK-29038 at 9/10/19 1:40 PM: -- [~cltlfcjin]

[jira] [Commented] (LIVY-489) Expose a JDBC endpoint for Livy

[ https://issues.apache.org/jira/browse/LIVY-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924894#comment-16924894 ] Marco Gaido commented on LIVY-489: -- The right place is the user mailing list, please see

[jira] [Commented] (LIVY-489) Expose a JDBC endpoint for Livy

[ https://issues.apache.org/jira/browse/LIVY-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924817#comment-16924817 ] Marco Gaido commented on LIVY-489: -- Yes, sure. The point is: that template in not exhaustive and does not

[jira] [Commented] (LIVY-489) Expose a JDBC endpoint for Livy

[ https://issues.apache.org/jira/browse/LIVY-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924812#comment-16924812 ] Marco Gaido commented on LIVY-489: -- [~vonatzki] nothing to be sorry about. Please see

[jira] [Commented] (SPARK-29009) Returning pojo from udf not working

[ https://issues.apache.org/jira/browse/SPARK-29009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924774#comment-16924774 ] Marco Gaido commented on SPARK-29009: - Why do you think this is a bug? If you want a struct to be

[jira] [Commented] (LIVY-489) Expose a JDBC endpoint for Livy

[ https://issues.apache.org/jira/browse/LIVY-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922363#comment-16922363 ] Marco Gaido commented on LIVY-489: -- Hi [~vonatzki]. Please check the design doc attached here. Moreover,

[jira] [Commented] (SPARK-28610) Support larger buffer for sum of long

[ https://issues.apache.org/jira/browse/SPARK-28610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921471#comment-16921471 ] Marco Gaido commented on SPARK-28610: - Hi [~Gengliang.Wang]. That's a different thing. you are doing

[jira] [Updated] (SPARK-28939) SQL configuration are not always propagated

[ https://issues.apache.org/jira/browse/SPARK-28939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido updated SPARK-28939: Description: The SQL configurations are propagated to executors in order to be effective.

[jira] [Created] (SPARK-28939) SQL configuration are not always propagated

Marco Gaido created SPARK-28939: --- Summary: SQL configuration are not always propagated Key: SPARK-28939 URL: https://issues.apache.org/jira/browse/SPARK-28939 Project: Spark Issue Type: Bug

[jira] [Commented] (SPARK-28916) Generated SpecificSafeProjection.apply method grows beyond 64 KB when use SparkSQL

[ https://issues.apache.org/jira/browse/SPARK-28916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16920153#comment-16920153 ] Marco Gaido commented on SPARK-28916: - I think the problem is related to subexpression elimination.

[jira] [Commented] (SPARK-28916) Generated SpecificSafeProjection.apply method grows beyond 64 KB when use SparkSQL

[ https://issues.apache.org/jira/browse/SPARK-28916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16920074#comment-16920074 ] Marco Gaido commented on SPARK-28916: - Thanks for reporting this. I am checking it. > Generated

[jira] [Commented] (SPARK-28934) Add `spark.sql.compatiblity.mode`

[ https://issues.apache.org/jira/browse/SPARK-28934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16920072#comment-16920072 ] Marco Gaido commented on SPARK-28934: - Hi [~smilegator]! Thanks for opening this. I am wondering

[jira] [Resolved] (LIVY-650) Remove schema from ResultSet

[ https://issues.apache.org/jira/browse/LIVY-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido resolved LIVY-650. -- Fix Version/s: 0.7.0 Resolution: Fixed Issue resolved by

[jira] [Resolved] (SPARK-28610) Support larger buffer for sum of long

[ https://issues.apache.org/jira/browse/SPARK-28610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido resolved SPARK-28610. - Resolution: Won't Fix Since the perf regression introduced by the change would be very high,

[jira] [Created] (LIVY-650) Remove schema from ResultSet

Marco Gaido created LIVY-650: Summary: Remove schema from ResultSet Key: LIVY-650 URL: https://issues.apache.org/jira/browse/LIVY-650 Project: Livy Issue Type: Improvement Components:

[jira] [Assigned] (LIVY-573) Add tests for operation logs retrieval

[ https://issues.apache.org/jira/browse/LIVY-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-573: Assignee: Yiheng Wang > Add tests for operation logs retrieval >

[jira] [Commented] (LIVY-627) Implement GetCrossReference metadata operation

[ https://issues.apache.org/jira/browse/LIVY-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16902733#comment-16902733 ] Marco Gaido commented on LIVY-627: -- Hi [~micahzhao]. Actually in Spark there is no primary key/foreign key

[jira] [Commented] (LIVY-575) Implement missing metadata operations

[ https://issues.apache.org/jira/browse/LIVY-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16900970#comment-16900970 ] Marco Gaido commented on LIVY-575: -- No problem, thank you. :) > Implement missing metadata operations >

[jira] [Assigned] (LIVY-627) Implement GetCrossReference metadata operation

[ https://issues.apache.org/jira/browse/LIVY-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-627: Assignee: (was: Yiheng Wang) > Implement GetCrossReference metadata operation >

[jira] [Comment Edited] (LIVY-575) Implement missing metadata operations

[ https://issues.apache.org/jira/browse/LIVY-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16900956#comment-16900956 ] Marco Gaido edited comment on LIVY-575 at 8/6/19 12:12 PM: --- [~yihengw] we assign

[jira] [Assigned] (LIVY-628) Implement GetDelegationToken metadata operation

[ https://issues.apache.org/jira/browse/LIVY-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-628: Assignee: (was: Yiheng Wang) > Implement GetDelegationToken metadata operation >

[jira] [Assigned] (LIVY-626) Implement GetPrimaryKeys metadata operation

[ https://issues.apache.org/jira/browse/LIVY-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-626: Assignee: (was: Yiheng Wang) > Implement GetPrimaryKeys metadata operation >

[jira] [Assigned] (LIVY-623) Implement GetTables metadata operation

[ https://issues.apache.org/jira/browse/LIVY-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-623: Assignee: (was: Yiheng Wang) > Implement GetTables metadata operation >

[jira] [Assigned] (LIVY-624) Implement GetColumns metadata operation

[ https://issues.apache.org/jira/browse/LIVY-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-624: Assignee: (was: Yiheng Wang) > Implement GetColumns metadata operation >

[jira] [Assigned] (LIVY-625) Implement GetFunctions metadata operation

[ https://issues.apache.org/jira/browse/LIVY-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-625: Assignee: (was: Yiheng Wang) > Implement GetFunctions metadata operation >

[jira] [Assigned] (LIVY-575) Implement missing metadata operations

[ https://issues.apache.org/jira/browse/LIVY-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-575: Assignee: (was: Yiheng Wang) > Implement missing metadata operations >

[jira] [Commented] (LIVY-575) Implement missing metadata operations

[ https://issues.apache.org/jira/browse/LIVY-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16900956#comment-16900956 ] Marco Gaido commented on LIVY-575: -- [~yihengw] we assign JIRAs when the related PRs are merged. Thanks. >

[jira] [Commented] (SPARK-28611) Histogram's height is diffrent

[ https://issues.apache.org/jira/browse/SPARK-28611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899585#comment-16899585 ] Marco Gaido commented on SPARK-28611: - Mmmhthat's weird! How can you get a different result than

[jira] [Created] (SPARK-28610) Support larger buffer for sum of long

Marco Gaido created SPARK-28610: --- Summary: Support larger buffer for sum of long Key: SPARK-28610 URL: https://issues.apache.org/jira/browse/SPARK-28610 Project: Spark Issue Type: Improvement

[jira] [Commented] (SPARK-28512) New optional mode: throw runtime exceptions on casting failures

[ https://issues.apache.org/jira/browse/SPARK-28512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892692#comment-16892692 ] Marco Gaido commented on SPARK-28512: - Thanks for pinging me [~maropu]. It is not the same issue, I

[jira] [Commented] (LIVY-575) Implement missing metadata operations

[ https://issues.apache.org/jira/browse/LIVY-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890784#comment-16890784 ] Marco Gaido commented on LIVY-575: -- Oh, you're right. Sorry for the mistake. > Implement missing metadata

[jira] [Commented] (LIVY-571) When an exception happens running a query, we should report it to end user

[ https://issues.apache.org/jira/browse/LIVY-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890785#comment-16890785 ] Marco Gaido commented on LIVY-571: -- Issue resolved by PR

[jira] [Issue Comment Deleted] (LIVY-575) Implement missing metadata operations

[ https://issues.apache.org/jira/browse/LIVY-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido updated LIVY-575: - Comment: was deleted (was: Issue resolved by PR https://github.com/apache/incubator-livy/pull/182.) >

[jira] [Assigned] (LIVY-571) When an exception happens running a query, we should report it to end user

[ https://issues.apache.org/jira/browse/LIVY-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-571: Assignee: Jeffrey(Xilang) Yan > When an exception happens running a query, we should report it to

[jira] [Resolved] (LIVY-575) Implement missing metadata operations

[ https://issues.apache.org/jira/browse/LIVY-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido resolved LIVY-575. -- Resolution: Fixed Fix Version/s: 0.7.0 Issue resolved by PR

[jira] [Commented] (SPARK-28470) Honor spark.sql.decimalOperations.nullOnOverflow in Cast

[ https://issues.apache.org/jira/browse/SPARK-28470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16889979#comment-16889979 ] Marco Gaido commented on SPARK-28470: - Thanks for checking this Wenchen! I will work on this ASAP.

[jira] [Resolved] (LIVY-598) Upgrade Livy jackson dependency to 2.9.9

[ https://issues.apache.org/jira/browse/LIVY-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido resolved LIVY-598. -- Resolution: Fixed Fix Version/s: 0.7.0 Issue resolved by

[jira] [Assigned] (LIVY-598) Upgrade Livy jackson dependency to 2.9.9

[ https://issues.apache.org/jira/browse/LIVY-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-598: Assignee: Arun Mahadevan > Upgrade Livy jackson dependency to 2.9.9 >

[jira] [Comment Edited] (SPARK-28225) Unexpected behavior for Window functions

[ https://issues.apache.org/jira/browse/SPARK-28225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16889518#comment-16889518 ] Marco Gaido edited comment on SPARK-28225 at 7/20/19 2:43 PM: -- Let me cite

[jira] [Commented] (SPARK-28225) Unexpected behavior for Window functions

[ https://issues.apache.org/jira/browse/SPARK-28225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16889518#comment-16889518 ] Marco Gaido commented on SPARK-28225: - Let me cite PostgreSQL documentation to explain you the

[jira] [Commented] (SPARK-28386) Cannot resolve ORDER BY columns with GROUP BY and HAVING

[ https://issues.apache.org/jira/browse/SPARK-28386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16889422#comment-16889422 ] Marco Gaido commented on SPARK-28386: - I think this is a duplicate of SPARK-26741. I have a PR for

[jira] [Commented] (LIVY-575) Implement missing metadata operations

[ https://issues.apache.org/jira/browse/LIVY-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16887734#comment-16887734 ] Marco Gaido commented on LIVY-575: -- HI [~yihengw]. Thanks for your help on this. I think it would be great

[jira] [Commented] (SPARK-23758) MLlib 2.4 Roadmap

[ https://issues.apache.org/jira/browse/SPARK-23758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886406#comment-16886406 ] Marco Gaido commented on SPARK-23758: - [~dongjoon] seems weird to set the affected version to 3.0

[jira] [Commented] (SPARK-28222) Feature importance outputs different values in GBT and Random Forest in 2.3.3 and 2.4 pyspark version

[ https://issues.apache.org/jira/browse/SPARK-28222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884412#comment-16884412 ] Marco Gaido commented on SPARK-28222: - [~eneriwrt] do you have a simple repro for this? I can try

[jira] [Commented] (SPARK-28316) Decimal precision issue

[ https://issues.apache.org/jira/browse/SPARK-28316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884398#comment-16884398 ] Marco Gaido commented on SPARK-28316: - Well, IIUC, this is just the result of Postgres having no

[jira] [Commented] (SPARK-28324) The LOG function using 10 as the base, but Spark using E

[ https://issues.apache.org/jira/browse/SPARK-28324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884397#comment-16884397 ] Marco Gaido commented on SPARK-28324: - +1 for [~srowen]'s opinion. I don't think it is a good idea

[jira] [Commented] (SPARK-28348) Avoid cast twice for decimal type

[ https://issues.apache.org/jira/browse/SPARK-28348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883165#comment-16883165 ] Marco Gaido commented on SPARK-28348: - Mmmhyes, you're right. > Avoid cast twice for decimal

[jira] [Commented] (SPARK-28348) Avoid cast twice for decimal type

[ https://issues.apache.org/jira/browse/SPARK-28348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882773#comment-16882773 ] Marco Gaido commented on SPARK-28348: - No, I don't think that's a good idea. Setting the result type

[jira] [Commented] (SPARK-28348) Avoid cast twice for decimal type

[ https://issues.apache.org/jira/browse/SPARK-28348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882741#comment-16882741 ] Marco Gaido commented on SPARK-28348: - There is no cast to `decimal(38, 6)`. The reson why the

[jira] [Comment Edited] (SPARK-28348) Avoid cast twice for decimal type

[ https://issues.apache.org/jira/browse/SPARK-28348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882741#comment-16882741 ] Marco Gaido edited comment on SPARK-28348 at 7/11/19 8:23 AM: -- There is no

[jira] [Commented] (SPARK-28322) DIV support decimal type

[ https://issues.apache.org/jira/browse/SPARK-28322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881798#comment-16881798 ] Marco Gaido commented on SPARK-28322: - Thanks for pinging me [~yumwang], I'll work on this on the

[jira] [Commented] (SPARK-28067) Incorrect results in decimal aggregation with whole-stage code gen enabled

[ https://issues.apache.org/jira/browse/SPARK-28067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880700#comment-16880700 ] Marco Gaido commented on SPARK-28067: - I cannot reproduce in 2.4.0 either: {code}

[jira] [Created] (SPARK-28235) Decimal sum return type

Marco Gaido created SPARK-28235: --- Summary: Decimal sum return type Key: SPARK-28235 URL: https://issues.apache.org/jira/browse/SPARK-28235 Project: Spark Issue Type: Improvement

[jira] [Commented] (SPARK-28222) Feature importance outputs different values in GBT and Random Forest in 2.3.3 and 2.4 pyspark version

[ https://issues.apache.org/jira/browse/SPARK-28222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877267#comment-16877267 ] Marco Gaido commented on SPARK-28222: - Mmmmh, there has been a bug fix for it (see SPARK-26721), but

[jira] [Commented] (SPARK-28186) array_contains returns null instead of false when one of the items in the array is null

[ https://issues.apache.org/jira/browse/SPARK-28186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876509#comment-16876509 ] Marco Gaido commented on SPARK-28186: - You're right with that. The equivalent in Postgres is

[jira] [Commented] (SPARK-28186) array_contains returns null instead of false when one of the items in the array is null

[ https://issues.apache.org/jira/browse/SPARK-28186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876357#comment-16876357 ] Marco Gaido commented on SPARK-28186: - Do you know of any SQL BD with the behavior you are

[jira] [Commented] (SPARK-28186) array_contains returns null instead of false when one of the items in the array is null

[ https://issues.apache.org/jira/browse/SPARK-28186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875447#comment-16875447 ] Marco Gaido commented on SPARK-28186: - This is the right behavior AFAIK. Why are you saying it is

[jira] [Commented] (SPARK-28201) Revisit MakeDecimal behavior on overflow

[ https://issues.apache.org/jira/browse/SPARK-28201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874765#comment-16874765 ] Marco Gaido commented on SPARK-28201: - I'll create a PR for this ASAP. > Revisit MakeDecimal

[jira] [Created] (SPARK-28201) Revisit MakeDecimal behavior on overflow

Marco Gaido created SPARK-28201: --- Summary: Revisit MakeDecimal behavior on overflow Key: SPARK-28201 URL: https://issues.apache.org/jira/browse/SPARK-28201 Project: Spark Issue Type: Bug

[jira] [Created] (SPARK-28200) Overflow handling in `ExpressionEncoder`

Marco Gaido created SPARK-28200: --- Summary: Overflow handling in `ExpressionEncoder` Key: SPARK-28200 URL: https://issues.apache.org/jira/browse/SPARK-28200 Project: Spark Issue Type: Bug

[jira] [Commented] (SPARK-28067) Incorrect results in decimal aggregation with whole-stage code gen enabled

[ https://issues.apache.org/jira/browse/SPARK-28067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870880#comment-16870880 ] Marco Gaido commented on SPARK-28067: - No, it is the same. Are you sure about your configs? {code}

[jira] [Commented] (SPARK-28135) ceil/ceiling/floor/power returns incorrect values

[ https://issues.apache.org/jira/browse/SPARK-28135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870360#comment-16870360 ] Marco Gaido commented on SPARK-28135: - [~Tonix517] tickets are assigned only once the PR is merged

[jira] [Commented] (SPARK-28067) Incorrect results in decimal aggregation with whole-stage code gen enabled

[ https://issues.apache.org/jira/browse/SPARK-28067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870293#comment-16870293 ] Marco Gaido commented on SPARK-28067: - I cannot reproduce on master. It always returns null with

[jira] [Commented] (SPARK-28060) Float/Double type can not accept some special inputs

[ https://issues.apache.org/jira/browse/SPARK-28060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870288#comment-16870288 ] Marco Gaido commented on SPARK-28060: - This is a duplicate of SPARK-27768, isn't it? Or better,

[jira] [Commented] (SPARK-27820) case insensitive resolver should be used in GetMapValue

[ https://issues.apache.org/jira/browse/SPARK-27820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870286#comment-16870286 ] Marco Gaido commented on SPARK-27820: - +1 for [~hyukjin.kwon]'s comment. > case insensitive

[jira] [Commented] (SPARK-28024) Incorrect numeric values when out of range

[ https://issues.apache.org/jira/browse/SPARK-28024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869879#comment-16869879 ] Marco Gaido commented on SPARK-28024: - [~joshrosen] thanks for linking them, Yes, I did try having

[jira] [Commented] (SPARK-24149) Automatic namespaces discovery in HDFS federation

[ https://issues.apache.org/jira/browse/SPARK-24149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851896#comment-16851896 ] Marco Gaido commented on SPARK-24149: - That's true, the point is: if you want to access a different

[jira] [Commented] (SPARK-24149) Automatic namespaces discovery in HDFS federation

[ https://issues.apache.org/jira/browse/SPARK-24149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848097#comment-16848097 ] Marco Gaido commented on SPARK-24149: - [~Dhruve Ashar] the use case for this change, for instance,

[jira] [Commented] (SPARK-27761) Make UDF nondeterministic by default(?)

[ https://issues.apache.org/jira/browse/SPARK-27761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16843914#comment-16843914 ] Marco Gaido commented on SPARK-27761: - Yes, I think this is a good idea IMHO. The behavior by

[jira] [Commented] (SPARK-27684) Reduce ScalaUDF conversion overheads for primitives

[ https://issues.apache.org/jira/browse/SPARK-27684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840242#comment-16840242 ] Marco Gaido commented on SPARK-27684: - I can try and work on it, but most likely I will start

[jira] [Commented] (SPARK-27684) Reduce ScalaUDF conversion overheads for primitives

[ https://issues.apache.org/jira/browse/SPARK-27684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839297#comment-16839297 ] Marco Gaido commented on SPARK-27684: - I agree on this too. > Reduce ScalaUDF conversion overheads

[jira] [Commented] (SPARK-27685) `union` doesn't promote non-nullable columns of struct to nullable

[ https://issues.apache.org/jira/browse/SPARK-27685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839295#comment-16839295 ] Marco Gaido commented on SPARK-27685: - This is a duplicate of SPARK-26812. > `union` doesn't

[jira] [Resolved] (SPARK-27685) `union` doesn't promote non-nullable columns of struct to nullable

[ https://issues.apache.org/jira/browse/SPARK-27685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido resolved SPARK-27685. - Resolution: Duplicate > `union` doesn't promote non-nullable columns of struct to nullable >

[jira] [Commented] (SPARK-26182) Cost increases when optimizing scalaUDF

[ https://issues.apache.org/jira/browse/SPARK-26182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16836486#comment-16836486 ] Marco Gaido commented on SPARK-26182: - Actually you just need to mark it {{asNondetermistic}} to

  1   2   3   4   5   6   7   8   >