Skip to content

Conversation

@gatorsmile
Copy link
Member

Revert the changes of #17646 made in Branch 2.1, because it breaks the build. It needs the parser interface, but SessionCatalog in branch 2.1 does not have it.

What changes were proposed in this pull request?

The session catalog caches some persistent functions in the FunctionRegistry, so there can be duplicates. Our Catalog API listFunctions does not handle it.

It would be better if SessionCatalog API can de-duplciate the records, instead of doing it by each API caller. In FunctionRegistry, our functions are identified by the unquoted string. Thus, this PR is try to parse it using our parser interface and then de-duplicate the names.

How was this patch tested?

Added test cases.

@SparkQA
Copy link

SparkQA commented Apr 17, 2017

Test build #75864 has finished for PR 17661 at commit 64c252e.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@rxin
Copy link
Contributor

rxin commented Apr 18, 2017

Merging in branch-2.1. Can you close your PR?

asfgit pushed a commit that referenced this pull request Apr 18, 2017
…functions after using persistent functions

Revert the changes of #17646 made in Branch 2.1, because it breaks the build. It needs the parser interface, but SessionCatalog in branch 2.1 does not have it.

### What changes were proposed in this pull request?

The session catalog caches some persistent functions in the `FunctionRegistry`, so there can be duplicates. Our Catalog API `listFunctions` does not handle it.

It would be better if `SessionCatalog` API can de-duplciate the records, instead of doing it by each API caller. In `FunctionRegistry`, our functions are identified by the unquoted string. Thus, this PR is try to parse it using our parser interface and then de-duplicate the names.

### How was this patch tested?
Added test cases.

Author: Xiao Li <[email protected]>

Closes #17661 from gatorsmile/compilationFix17646.
@gatorsmile gatorsmile closed this Apr 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants