[
https://issues.apache.org/jira/browse/SPARK-27764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278065#comment-17278065
]
Attila Zsolt Piros commented on SPARK-27764:
--------------------------------------------
Sorry to chime in but we have (after SPARK-30374 and SPARK-30375) 55 open
sub-tasks, are this 55 sub-task closeable?
I am asking as I happen to start work on one of those (it was SPARK-29391) and
after some work it turned out it is not needed and this is a bit frustrating.
I am offering my help too to avoid further unnecessary frustration for the
others who would start to work on a issue but we have to discuss our strategy
first.
If it is closable then let's close it. If we need to go through one by one then
let's divide it among us.
Or should I just go ahead give one or two weeks grace period before closing it?
How can I help here?
> Feature Parity between PostgreSQL and Spark
> -------------------------------------------
>
> Key: SPARK-27764
> URL: https://issues.apache.org/jira/browse/SPARK-27764
> Project: Spark
> Issue Type: Umbrella
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Xiao Li
> Priority: Major
>
> PostgreSQL is one of the most advanced open source databases. This umbrella
> Jira is trying to track the missing features and bugs.
> UPDATED: This umbrella tickets basically intend to include bug reports and
> general issues for the feature parity. For implementation-dependent
> behaviours and ANS/SQL standard topics, you need to check the two umbrella
> below;
> - SPARK-30374 Feature Parity between PostgreSQL and Spark (ANSI/SQL)
> - SPARK-30375 Feature Parity between PostgreSQL and Spark
> (implementation-dependent behaviours)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
