Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15634
**[Test build #67717 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67717/consoleFull)**
for PR 15634 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15634
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67717/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15634
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15634
**[Test build #67717 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67717/consoleFull)**
for PR 15634 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15634
FileIndex sounds good to me. I wouldn't call it "Metastore" though, since
that is a Hive specific term. I'd call it Catalog.
---
If your project is set up for it, you can reply to this email and
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/15634
Concretely, I propose renaming
```
TableFileCatalog => MetastoreFileIndex
ListingFileCatalog => InMemoryFileIndex
MetadataLogFileCatalog => MetadataLogFileIndex
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/15634
How about `FileIndex`, since this class is responsible for both listing and
filtering functionality?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15634
FileLister? FileListing?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/15634
Hmm, any other suggestions?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/15634
This is okay, but note that "Provider" is equally overloaded in the Data
Source API.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15634
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15634
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67544/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15634
**[Test build #67544 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67544/consoleFull)**
for PR 15634 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15634
**[Test build #67544 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67544/consoleFull)**
for PR 15634 at commit
14 matches
Mail list logo
