Github user JamesRTaylor commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/153#discussion_r57581391
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java ---
@@ -544,7 +556,28 @@ private MetaDataMutationResult updateCache(PName
tenantId, String schemaName, St
return result;
}
-
+
+ public MetaDataMutationResult updateCache(String schemaName) throws
SQLException {
+ return updateCache(schemaName, false);
+ }
+
+ public MetaDataMutationResult updateCache(String schemaName, boolean
alwaysHitServer) throws SQLException {
+ long clientTimeStamp = getClientTimeStamp();
+ PSchema schema = null;
+ try {
+ schema = connection.getMetaDataCache().getSchema(new
PTableKey(null, schemaName));
--- End diff --
No, we wouldn't need a schema per tenantId. With namespace support, is all
data still stored in the same physical table for all views, even if the views
have different schemas? For example, given the following:
CREATE VIEW s1.a AS SELECT * FROM t WHERE k=1;
CREATE VIEW s2.b AS SELECT * FROM t WHERE k=2;
CREATE VIEW s3.c AS SELECT * FROM t WHERE k=3;
Would the following query still return all rows across all three views?
SELECT * FROM t;
---
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 so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
