Github user ankitsinghal commented on the pull request:
https://github.com/apache/phoenix/pull/153#issuecomment-200264320
Currently ,VIEW can be created in different schema name than it's base
table name. are you recommending to use same schema?
I checked MySQL and postgres and they also allow creation of VIEW in
different namespace/schema than its physical table. (may be it's because VIEW
is logical and can be created on joined tables residing in different namespaces
[though phoenix doesn't support join query in VIEW currently])
http://dev.mysql.com/doc/refman/5.7/en/create-view.html
http://www.postgresql.org/docs/9.2/static/sql-createview.html
"If a schema name is given (for example, CREATE VIEW myschema.myview ...)
then the view is created in the specified schema. Otherwise it is created in
the current schema"
What do you think about VIEW Indexes created with different schema as they
all share a single physical table for storage and currently with above changes
we are keeping a index table in same hbase namespace as of it's base/physical
table.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
