[ https://issues.apache.org/jira/browse/SPARK-43041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709208#comment-17709208 ]
ci-cassandra.apache.org commented on SPARK-43041: ------------------------------------------------- User 'aokolnychyi' has created a pull request for this issue: https://github.com/apache/spark/pull/40679 > Restore constructors of exceptions for compatibility in connector API > --------------------------------------------------------------------- > > Key: SPARK-43041 > URL: https://issues.apache.org/jira/browse/SPARK-43041 > Project: Spark > Issue Type: Bug > Components: Spark Core > Affects Versions: 3.4.0 > Reporter: Xinrong Meng > Assignee: Anton Okolnychyi > Priority: Blocker > Fix For: 3.4.0 > > > Thanks [~aokolnychyi] for raising the issue as shown below: > {quote} > I have a question about changes to exceptions used in the public connector > API, such as NoSuchTableException and TableAlreadyExistsException. > I consider those as part of the public Catalog API (TableCatalog uses them in > method definitions). However, it looks like PR #37887 has changed them in an > incompatible way. Old constructors accepting Identifier objects got removed. > The only way to construct such exceptions is either by passing database and > table strings or Scala Seq. Shall we add back old constructors to avoid > breaking connectors? > {quote} > We should restore constructors of those exceptions to preserve the > compatibility in connector API. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org