[jira] [Assigned] (SPARK-33668) Fix flaky test "Verify logging configuration is picked from the provided SPARK_CONF_DIR/log4j.properties."

[ https://issues.apache.org/jira/browse/SPARK-33668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun reassigned SPARK-33668: - Assignee: Prashant Sharma > Fix flaky test "Verify logging configuration is picked

[jira] [Resolved] (SPARK-33668) Fix flaky test "Verify logging configuration is picked from the provided SPARK_CONF_DIR/log4j.properties."

[ https://issues.apache.org/jira/browse/SPARK-33668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun resolved SPARK-33668. --- Fix Version/s: 3.2.0 Resolution: Fixed Issue resolved by pull request 30616

[jira] [Resolved] (SPARK-33661) Unable to load RandomForestClassificationModel trained in Spark 2.x

[ https://issues.apache.org/jira/browse/SPARK-33661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon resolved SPARK-33661. -- Resolution: Not A Problem > Unable to load RandomForestClassificationModel trained in Spark

[jira] [Commented] (SPARK-33661) Unable to load RandomForestClassificationModel trained in Spark 2.x

[ https://issues.apache.org/jira/browse/SPARK-33661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244638#comment-17244638 ] Hyukjin Kwon commented on SPARK-33661: -- There's a major version bumped up from 2 -> 3. Breaking

[jira] [Resolved] (SPARK-33648) Moving file stage failed cause dulpicated data

[ https://issues.apache.org/jira/browse/SPARK-33648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon resolved SPARK-33648. -- Resolution: Invalid [~blackpig] please fill the JIRA description. > Moving file stage failed

[jira] [Commented] (SPARK-33256) Update contribution guide about NumPy documentation style

[ https://issues.apache.org/jira/browse/SPARK-33256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244645#comment-17244645 ] Hyukjin Kwon commented on SPARK-33256: -- We should have a page like

[jira] [Created] (SPARK-33674) Show Slowpoke notifications in SBT tests

Xiao Li created SPARK-33674: --- Summary: Show Slowpoke notifications in SBT tests Key: SPARK-33674 URL: https://issues.apache.org/jira/browse/SPARK-33674 Project: Spark Issue Type: Test

[jira] [Updated] (SPARK-32991) RESET can clear StaticSQLConfs

[ https://issues.apache.org/jira/browse/SPARK-32991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-32991: Priority: Blocker (was: Major) > RESET can clear StaticSQLConfs > -- > >

[jira] [Commented] (SPARK-32991) RESET can clear StaticSQLConfs

[ https://issues.apache.org/jira/browse/SPARK-32991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244675#comment-17244675 ] Xiao Li commented on SPARK-32991: - [~Qin Yao] I reopened the Jira and set it to Blocker, because the

[jira] [Assigned] (SPARK-33674) Show Slowpoke notifications in SBT tests

[ https://issues.apache.org/jira/browse/SPARK-33674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33674: Assignee: Apache Spark (was: Xiao Li) > Show Slowpoke notifications in SBT tests >

[jira] [Assigned] (SPARK-33674) Show Slowpoke notifications in SBT tests

[ https://issues.apache.org/jira/browse/SPARK-33674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33674: Assignee: Xiao Li (was: Apache Spark) > Show Slowpoke notifications in SBT tests >

[jira] [Commented] (SPARK-33674) Show Slowpoke notifications in SBT tests

[ https://issues.apache.org/jira/browse/SPARK-33674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244647#comment-17244647 ] Apache Spark commented on SPARK-33674: -- User 'gatorsmile' has created a pull request for this

[jira] [Commented] (SPARK-33674) Show Slowpoke notifications in SBT tests

[ https://issues.apache.org/jira/browse/SPARK-33674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244646#comment-17244646 ] Apache Spark commented on SPARK-33674: -- User 'gatorsmile' has created a pull request for this

[jira] [Commented] (SPARK-33256) Update contribution guide about NumPy documentation style

[ https://issues.apache.org/jira/browse/SPARK-33256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244648#comment-17244648 ] Apache Spark commented on SPARK-33256: -- User 'HyukjinKwon' has created a pull request for this

[jira] [Assigned] (SPARK-33256) Update contribution guide about NumPy documentation style

[ https://issues.apache.org/jira/browse/SPARK-33256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33256: Assignee: Apache Spark > Update contribution guide about NumPy documentation style >

[jira] [Assigned] (SPARK-33256) Update contribution guide about NumPy documentation style

[ https://issues.apache.org/jira/browse/SPARK-33256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33256: Assignee: (was: Apache Spark) > Update contribution guide about NumPy documentation

[jira] [Reopened] (SPARK-32991) RESET can clear StaticSQLConfs

[ https://issues.apache.org/jira/browse/SPARK-32991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li reopened SPARK-32991: - > RESET can clear StaticSQLConfs > -- > > Key: SPARK-32991 >

[jira] [Resolved] (SPARK-33637) Spark sql drop non-existent table will not report an error after failure

[ https://issues.apache.org/jira/browse/SPARK-33637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon resolved SPARK-33637. -- Resolution: Invalid No feedback from the reporter. > Spark sql drop non-existent table will

[jira] [Commented] (SPARK-33639) The external table does not specify a location

[ https://issues.apache.org/jira/browse/SPARK-33639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244640#comment-17244640 ] Hyukjin Kwon commented on SPARK-33639: -- [~guihuawen] what is the actual result and expected result?

[jira] [Commented] (SPARK-33256) Update contribution guide about NumPy documentation style

[ https://issues.apache.org/jira/browse/SPARK-33256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244649#comment-17244649 ] Apache Spark commented on SPARK-33256: -- User 'HyukjinKwon' has created a pull request for this

[jira] [Updated] (SPARK-32991) RESET can clear StaticSQLConfs

[ https://issues.apache.org/jira/browse/SPARK-32991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-32991: Target Version/s: 3.1.0 > RESET can clear StaticSQLConfs > -- > >

[jira] [Commented] (SPARK-33044) Add a Jenkins build and test job for Scala 2.13

[ https://issues.apache.org/jira/browse/SPARK-33044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244672#comment-17244672 ] Dongjoon Hyun commented on SPARK-33044: --- I don't think so, [~srowen]. And, new Jenkins servers

[jira] [Resolved] (SPARK-32348) Get tests working for Scala 2.13 build

[ https://issues.apache.org/jira/browse/SPARK-32348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen resolved SPARK-32348. -- Fix Version/s: 3.1.0 Resolution: Fixed This should be largely done now, or at least,

[jira] [Commented] (SPARK-33044) Add a Jenkins build and test job for Scala 2.13

[ https://issues.apache.org/jira/browse/SPARK-33044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244604#comment-17244604 ] Sean R. Owen commented on SPARK-33044: -- [~dongjoon] This is done now right? > Add a Jenkins build

[jira] [Updated] (SPARK-33285) Too many "Auto-application to `()` is deprecated." related compilation warnings

[ https://issues.apache.org/jira/browse/SPARK-33285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen updated SPARK-33285: - Parent: (was: SPARK-25075) Issue Type: Improvement (was: Sub-task) > Too many

[jira] [Updated] (SPARK-33344) Fix Compilation warings of "multiarg infix syntax looks like a tuple and will be deprecated" in Scala 2.13

[ https://issues.apache.org/jira/browse/SPARK-33344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen updated SPARK-33344: - Parent: (was: SPARK-25075) Issue Type: Improvement (was: Sub-task) > Fix

[jira] [Commented] (SPARK-33285) Too many "Auto-application to `()` is deprecated." related compilation warnings

[ https://issues.apache.org/jira/browse/SPARK-33285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244605#comment-17244605 ] Sean R. Owen commented on SPARK-33285: -- I moved this out from the 2.13 umbrella as it is not

[jira] [Updated] (SPARK-33344) Fix Compilation warnings of "multiarg infix syntax looks like a tuple and will be deprecated" in Scala 2.13

[ https://issues.apache.org/jira/browse/SPARK-33344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen updated SPARK-33344: - Summary: Fix Compilation warnings of "multiarg infix syntax looks like a tuple and will be

[jira] [Commented] (SPARK-33348) Use scala.jdk.CollectionConverters replace scala.collection.JavaConverters

[ https://issues.apache.org/jira/browse/SPARK-33348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244607#comment-17244607 ] Sean R. Owen commented on SPARK-33348: -- Yes, this isn't required for 2.13, and can't be done for

[jira] [Updated] (SPARK-33355) Batch fix compilation warnings about "method copyArrayToImmutableIndexedSeq in class LowPriorityImplicits2 is deprecated (since 2.13.0)"

[ https://issues.apache.org/jira/browse/SPARK-33355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen updated SPARK-33355: - Parent: (was: SPARK-25075) Issue Type: Improvement (was: Sub-task) > Batch fix

[jira] [Resolved] (SPARK-33499) Enable `-Wunused:imports` in Scala 2.13 SBT

[ https://issues.apache.org/jira/browse/SPARK-33499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen resolved SPARK-33499. -- Resolution: Not A Problem OK, so we don't remove it. I don't see the issue. > Enable

[jira] [Updated] (SPARK-33499) Enable `-Wunused:imports` in Scala 2.13 SBT

[ https://issues.apache.org/jira/browse/SPARK-33499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen updated SPARK-33499: - Parent: (was: SPARK-25075) Issue Type: Improvement (was: Sub-task) > Enable

[jira] [Updated] (SPARK-33345) Batch fix compilation warnings about "Widening conversion from XXX to XXX is deprecated"

[ https://issues.apache.org/jira/browse/SPARK-33345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen updated SPARK-33345: - Parent: (was: SPARK-25075) Issue Type: Improvement (was: Sub-task) > Batch fix

[jira] [Updated] (SPARK-33348) Use scala.jdk.CollectionConverters replace scala.collection.JavaConverters

[ https://issues.apache.org/jira/browse/SPARK-33348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean R. Owen updated SPARK-33348: - Parent: (was: SPARK-25075) Issue Type: Improvement (was: Sub-task) > Use

[jira] [Created] (SPARK-33673) Do not push down partition filters to ParquetScan for DataSourceV2

Yuming Wang created SPARK-33673: --- Summary: Do not push down partition filters to ParquetScan for DataSourceV2 Key: SPARK-33673 URL: https://issues.apache.org/jira/browse/SPARK-33673 Project: Spark

[jira] [Commented] (SPARK-33673) Do not push down partition filters to ParquetScan for DataSourceV2

[ https://issues.apache.org/jira/browse/SPARK-33673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244612#comment-17244612 ] Yuming Wang commented on SPARK-33673: - [~cloud_fan] [~rdblue] [~viirya] > Do not push down

[jira] [Commented] (SPARK-33673) Do not push down partition filters to ParquetScan for DataSourceV2

[ https://issues.apache.org/jira/browse/SPARK-33673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244615#comment-17244615 ] L. C. Hsieh commented on SPARK-33673: - You mean these test failed once upgrading to Parquet 1.11.1?

[jira] [Commented] (SPARK-33673) Do not push down partition filters to ParquetScan for DataSourceV2

[ https://issues.apache.org/jira/browse/SPARK-33673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244624#comment-17244624 ] Yuming Wang commented on SPARK-33673: - Yes, you can verify it by: {code:sh} mvn -Dtest=none

[jira] [Commented] (SPARK-33670) Verify the partition provider is Hive in v1 SHOW TABLE EXTENDED

[ https://issues.apache.org/jira/browse/SPARK-33670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244486#comment-17244486 ] Apache Spark commented on SPARK-33670: -- User 'MaxGekk' has created a pull request for this issue:

[jira] [Created] (SPARK-33670) Verify the partition provider is Hive in v1 SHOW TABLE EXTENDED

Maxim Gekk created SPARK-33670: -- Summary: Verify the partition provider is Hive in v1 SHOW TABLE EXTENDED Key: SPARK-33670 URL: https://issues.apache.org/jira/browse/SPARK-33670 Project: Spark

[jira] [Created] (SPARK-33669) Wrong error message from YARN application state monitor when sc.stop in yarn client mode

Su Qilong created SPARK-33669: - Summary: Wrong error message from YARN application state monitor when sc.stop in yarn client mode Key: SPARK-33669 URL: https://issues.apache.org/jira/browse/SPARK-33669

[jira] [Updated] (SPARK-33669) Wrong error message from YARN application state monitor when sc.stop in yarn client mode

[ https://issues.apache.org/jira/browse/SPARK-33669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Qilong updated SPARK-33669: -- Description: For YarnClient mode, when stopping YarnClientSchedulerBackend, it first tries to

[jira] [Updated] (SPARK-33669) Wrong error message from YARN application state monitor when sc.stop in yarn client mode

[ https://issues.apache.org/jira/browse/SPARK-33669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Qilong updated SPARK-33669: -- Description: For YarnClient mode, when stopping YarnClientSchedulerBackend, it first tries to

[jira] [Commented] (SPARK-33669) Wrong error message from YARN application state monitor when sc.stop in yarn client mode

[ https://issues.apache.org/jira/browse/SPARK-33669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244456#comment-17244456 ] Apache Spark commented on SPARK-33669: -- User 'sqlwindspeaker' has created a pull request for this

[jira] [Commented] (SPARK-33669) Wrong error message from YARN application state monitor when sc.stop in yarn client mode

[ https://issues.apache.org/jira/browse/SPARK-33669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244455#comment-17244455 ] Apache Spark commented on SPARK-33669: -- User 'sqlwindspeaker' has created a pull request for this

[jira] [Commented] (SPARK-33668) Fix flaky test "Verify logging configuration is picked from the provided SPARK_CONF_DIR/log4j.properties."

[ https://issues.apache.org/jira/browse/SPARK-33668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244433#comment-17244433 ] Apache Spark commented on SPARK-33668: -- User 'ScrapCodes' has created a pull request for this

[jira] [Assigned] (SPARK-33668) Fix flaky test "Verify logging configuration is picked from the provided SPARK_CONF_DIR/log4j.properties."

[ https://issues.apache.org/jira/browse/SPARK-33668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33668: Assignee: Apache Spark > Fix flaky test "Verify logging configuration is picked from the

[jira] [Commented] (SPARK-33668) Fix flaky test "Verify logging configuration is picked from the provided SPARK_CONF_DIR/log4j.properties."

[ https://issues.apache.org/jira/browse/SPARK-33668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244434#comment-17244434 ] Apache Spark commented on SPARK-33668: -- User 'ScrapCodes' has created a pull request for this

[jira] [Assigned] (SPARK-33668) Fix flaky test "Verify logging configuration is picked from the provided SPARK_CONF_DIR/log4j.properties."

[ https://issues.apache.org/jira/browse/SPARK-33668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33668: Assignee: (was: Apache Spark) > Fix flaky test "Verify logging configuration is

[jira] [Updated] (SPARK-33669) Wrong error message from YARN application state monitor when sc.stop in yarn client mode

[ https://issues.apache.org/jira/browse/SPARK-33669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Qilong updated SPARK-33669: -- Description: For YarnClient mode, when stopping YarnClientSchedulerBackend, it first tries to

[jira] [Updated] (SPARK-33669) Wrong error message from YARN application state monitor when sc.stop in yarn client mode

[ https://issues.apache.org/jira/browse/SPARK-33669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Qilong updated SPARK-33669: -- Description: For YarnClient mode, when stopping YarnClientSchedulerBackend, it first tries to

[jira] [Assigned] (SPARK-33669) Wrong error message from YARN application state monitor when sc.stop in yarn client mode

[ https://issues.apache.org/jira/browse/SPARK-33669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33669: Assignee: Apache Spark > Wrong error message from YARN application state monitor when

[jira] [Assigned] (SPARK-33669) Wrong error message from YARN application state monitor when sc.stop in yarn client mode

[ https://issues.apache.org/jira/browse/SPARK-33669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33669: Assignee: (was: Apache Spark) > Wrong error message from YARN application state

[jira] [Updated] (SPARK-33669) Wrong error message from YARN application state monitor when sc.stop in yarn client mode

[ https://issues.apache.org/jira/browse/SPARK-33669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Qilong updated SPARK-33669: -- Description: For YarnClient mode, when stopping YarnClientSchedulerBackend, it first tries to

[jira] [Assigned] (SPARK-33670) Verify the partition provider is Hive in v1 SHOW TABLE EXTENDED

[ https://issues.apache.org/jira/browse/SPARK-33670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33670: Assignee: Apache Spark > Verify the partition provider is Hive in v1 SHOW TABLE EXTENDED

[jira] [Assigned] (SPARK-33670) Verify the partition provider is Hive in v1 SHOW TABLE EXTENDED

[ https://issues.apache.org/jira/browse/SPARK-33670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33670: Assignee: (was: Apache Spark) > Verify the partition provider is Hive in v1 SHOW

[jira] [Assigned] (SPARK-33670) Verify the partition provider is Hive in v1 SHOW TABLE EXTENDED

[ https://issues.apache.org/jira/browse/SPARK-33670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33670: Assignee: Apache Spark > Verify the partition provider is Hive in v1 SHOW TABLE EXTENDED

[jira] [Commented] (SPARK-31711) Register the executor source with the metrics system when running in local mode.

[ https://issues.apache.org/jira/browse/SPARK-31711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244496#comment-17244496 ] Apache Spark commented on SPARK-31711: -- User 'LucaCanali' has created a pull request for this

[jira] [Assigned] (SPARK-33671) Remove VIEW checks from V1 table commands

[ https://issues.apache.org/jira/browse/SPARK-33671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33671: Assignee: (was: Apache Spark) > Remove VIEW checks from V1 table commands >

[jira] [Assigned] (SPARK-33671) Remove VIEW checks from V1 table commands

[ https://issues.apache.org/jira/browse/SPARK-33671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33671: Assignee: Apache Spark > Remove VIEW checks from V1 table commands >

[jira] [Commented] (SPARK-33671) Remove VIEW checks from V1 table commands

[ https://issues.apache.org/jira/browse/SPARK-33671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244536#comment-17244536 ] Apache Spark commented on SPARK-33671: -- User 'MaxGekk' has created a pull request for this issue:

[jira] [Created] (SPARK-33672) Check SQLContext.tables() for V2 session catalog

Maxim Gekk created SPARK-33672: -- Summary: Check SQLContext.tables() for V2 session catalog Key: SPARK-33672 URL: https://issues.apache.org/jira/browse/SPARK-33672 Project: Spark Issue Type:

[jira] [Commented] (SPARK-31711) Register the executor source with the metrics system when running in local mode.

[ https://issues.apache.org/jira/browse/SPARK-31711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244497#comment-17244497 ] Apache Spark commented on SPARK-31711: -- User 'LucaCanali' has created a pull request for this

[jira] [Commented] (SPARK-33672) Check SQLContext.tables() for V2 session catalog

[ https://issues.apache.org/jira/browse/SPARK-33672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244542#comment-17244542 ] Maxim Gekk commented on SPARK-33672: [~cloud_fan] FYI > Check SQLContext.tables() for V2 session

[jira] [Created] (SPARK-33671) Remove VIEW checks from V1 table commands

Maxim Gekk created SPARK-33671: -- Summary: Remove VIEW checks from V1 table commands Key: SPARK-33671 URL: https://issues.apache.org/jira/browse/SPARK-33671 Project: Spark Issue Type: Sub-task

[jira] [Commented] (SPARK-33671) Remove VIEW checks from V1 table commands

[ https://issues.apache.org/jira/browse/SPARK-33671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17244538#comment-17244538 ] Apache Spark commented on SPARK-33671: -- User 'MaxGekk' has created a pull request for this issue: