| commit | 48552646982ff08f202536700766ca3660daacf5 | |
| author | Tatiana Racheva <tatianaracheva@fb.com> | |
| Fri, 12 Jul 2019 19:55:19 +0000 (12 12:55 -0700) | ||
| committer | Hhvm Bot <hhvm-bot@users.noreply.github.com> | |
| Fri, 12 Jul 2019 20:02:22 +0000 (12 13:02 -0700) | ||
| tree | 8057ef69785abd115b70e5a19a3c19b23697ce5a | treesnapshot (tar.gz zip) |
| parent | 2636cd4f4fe2f9b4c8e35669bc2234edee7e05ec | commitdiff |
Explose naming table SQLite path
Summary: I want to use this path to determine whether to parallelize iteration over the naming table to MultiWorker (if it's SQLite-based) or to use the old way. Can also be used to decide whether to create a new naming table or to write incremental updates to an existing one.
Reviewed By: jewelpit
Differential Revision: D16216650
fbshipit-source-id: f911b9ac7f4b321cad0d410fe19f397f7ed2beaf
Summary: I want to use this path to determine whether to parallelize iteration over the naming table to MultiWorker (if it's SQLite-based) or to use the old way. Can also be used to decide whether to create a new naming table or to write incremental updates to an existing one.
Reviewed By: jewelpit
Differential Revision: D16216650
fbshipit-source-id: f911b9ac7f4b321cad0d410fe19f397f7ed2beaf
| hphp/hack/src/naming/naming_table.ml | diffblobblamehistory | |
| hphp/hack/src/naming/naming_table.mli | diffblobblamehistory | |
| hphp/hack/test/unit/naming/naming_table_tests.ml | diffblobblamehistory |