Transferring metadata from immutable storage
The subject technology generates and stores a new version set of one or more table-metadata files, the new version set of one or more table-metadata files comprising table metadata for a new version of a database table. The subject technology determines that a plurality of table-metadata files are not included in a cache. The subject technology downloads, in parallel, the plurality of table-metadata files from immutable storage. The subject technology stores, in the cache, the plurality of table-metadata files. The subject technology reads, among the plurality of table-metadata files, a first table-metadata file before a second table-metadata file has been fully downloaded, the plurality of table-metadata files comprising at least the first table-metadata file and the second table-metadata file.
1. A method comprising:
generating and storing a new version set of one or more table-metadata files, the new version set of one or more table-metadata files comprising table metadata for a new version of a database table;
determining that a plurality of table-metadata files are not included in a cache;
downloading, in parallel, the plurality of table-metadata files from immutable storage;
storing, in the cache, the plurality of table-metadata files; and
reading, among the plurality of table-metadata files, a first table-metadata file before a second table-metadata file has been fully downloaded, the plurality of table-metadata files comprising at least the first table-metadata file and the second table-metadata file.
2. The method of claim 1 , wherein reading the first table-metadata file occurs during a process for generating a scan set of table-metadata files.
3. The method of claim 2 , further comprising:
reading, among the plurality of table-metadata files, the second table-metadata file after the second table-metadata file has been downloaded.
4. The method of claim 3 , further comprising:
providing the scan set to an execution node to retrieve table data files for processing a query.
5. The method of claim 1 , further comprising:
caching, in connection with processing a first query, one or more of table-metadata files in at least one of a current version set of one or more table-metadata files and a new version set of one or more table-metadata files.
6. The method of claim 5 , wherein the one or more of table-metadata files are cached in a local cache within at least one cluster of an execution platform.
7. The method of claim 5 , further comprising:
receiving a subsequent query directed to the database table;
downloading, in connection with processing the subsequent query, at least one uncached table-metadata file in a scan set of table-metadata files for the subsequent query; and
processing the subsequent query using the at least one uncached table-metadata file.
8. The method of claim 7 , wherein the scan set of table-metadata files indicates at least one table-metadata file for performing the subsequent query.
9. The method of claim 1 , further comprising:
determining first version number of a current version set of one or more table-data files;
determining a second version number of a particular version set of the table-metadata files that is smaller or equal to than the first version number; and
generating a scan set of the table-metadata files based on the particular version set of the table-metadata files.
10. The method of claim 9 , wherein the smaller number indicates that at least a portion of one new table-metadata file has yet to be stored in immutable storage.
11. A system comprising:
at least one processor; and
a memory device including instructions, which when executed by the at least one processor, cause the at least one processor to perform operations comprising:
generating and storing a new version set of one or more table-metadata files, the new version set of one or more table-metadata files comprising table metadata for a new version of a database table;
determining that a plurality of table-metadata files are not included in a cache;
downloading, in parallel, the plurality of table-metadata files from immutable storage;
storing, in the cache, the plurality of table-metadata files; and
reading, among the plurality of table-metadata files, a first table-metadata file before a second table-metadata file has been fully downloaded, the plurality of table-metadata files comprising at least the first table-metadata file and the second table-metadata file.
12. The system of claim 11 , wherein reading the first table-metadata file occurs during a process for generating a scan set of table-metadata files.
13. The system of claim 12 , wherein the operations further comprise:
reading, among the plurality of table-metadata files, the second table-metadata file after the second table-metadata file has been downloaded.
14. The system of claim 13 , wherein the operations further comprise:
providing the scan set to an execution node to retrieve table data files for processing a query.
15. The system of claim 11 , wherein the operations further comprise:
caching, in connection with processing a first query, one or more of table-metadata files in at least one of a current version set of one or more table-metadata files and a new version set of one or more table-metadata files.
16. The system of claim 15 , wherein the one or more of table-metadata files are cached in a local cache within at least one cluster of an execution platform.
17. The system of claim 15 , wherein the operations further comprise:
receiving a subsequent query directed to the database table;
downloading, in connection with processing the subsequent query, at least one uncached table-metadata file in a scan set of table-metadata files for the subsequent query; and
processing the subsequent query using the at least one uncached table-metadata file.
18. The system of claim 17 , wherein the scan set of table-metadata files indicates at least one table-metadata file for performing the subsequent query.
19. The system of claim 11 , wherein the operations further comprise:
determining first version number of a current version set of one or more table-data files;
determining a second version number of a particular version set of the table-metadata files that is smaller or equal to than the first version number; and
generating a scan set of the table-metadata files based on the particular version set of the table-metadata files.
20. The system of claim 19 , wherein the smaller number indicates that at least a portion of one new table-metadata file has yet to be stored in immutable storage.
21. A non-transitory computer-readable medium comprising instructions, which when executed by at least one processor, cause the at least one processor to perform operations comprising:
generating and storing a new version set of one or more table-metadata files, the new version set of one or more table-metadata files comprising table metadata for a new version of a database table;
determining that a plurality of table-metadata files are not included in a cache;
downloading, in parallel, the plurality of table-metadata files from immutable storage;
storing, in the cache, the plurality of table-metadata files; and
reading, among the plurality of table-metadata files, a first table-metadata file before a second table-metadata file has been fully downloaded, the plurality of table-metadata files comprising at least the first table-metadata file and the second table-metadata file.
22. The non-transitory computer-readable medium of claim 21 , wherein reading the first table-metadata file occurs during a process for generating a scan set of table-metadata files.
23. The non-transitory computer-readable medium of claim 22 , wherein the operations further comprise:
reading, among the plurality of table-metadata files, the second table-metadata file after the second table-metadata file has been downloaded.
24. The non-transitory computer-readable medium of claim 23 , wherein the operations further comprise:
providing the scan set to an execution node to retrieve table data files for processing a query.
25. The non-transitory computer-readable medium of claim 21 , wherein the operations further comprise:
caching, in connection with processing a first query, one or more of table-metadata files in at least one of a current version set of one or more table-metadata files and a new version set of one or more table-metadata files.
26. The non-transitory computer-readable medium of claim 25 , wherein the one or more of table-metadata files are cached in a local cache within at least one cluster of an execution platform.
27. The non-transitory computer-readable medium of claim 25 , wherein the operations further comprise:
receiving a subsequent query directed to the database table;
downloading, in connection with processing the subsequent query, at least one uncached table-metadata file in a scan set of table-metadata files for the subsequent query; and
processing the subsequent query using the at least one uncached table-metadata file.
28. The non-transitory computer-readable medium of claim 27 , wherein the scan set of table-metadata files indicates at least one table-metadata file for performing the subsequent query.
29. The non-transitory computer-readable medium of claim 21 , wherein the operations further comprise:
determining first version number of a current version set of one or more table-data files;
determining a second version number of a particular version set of the table-metadata files that is smaller or equal to than the first version number; and
generating a scan set of the table-metadata files based on the particular version set of the table-metadata files.
30. The non-transitory computer-readable medium of claim 29 , wherein the smaller number indicates that at least a portion of one new table-metadata file has yet to be stored in immutable storage.