Uh oh!
There was an error while loading. Please reload this page.
PHOENIX-6506 : Tenant Connection is not able to access/validate Global Sequences - #1261
Conversation
stoty
commented
Jul 7, 2021
💔 -1 overall
This message was automatically generated. |
mnpoonia
commented
Jul 15, 2021
@lokiore - Looks like there are checkstyle issues and some unit test are failing |
virajjasani
left a comment
There was a problem hiding this comment.
Skimmed, left few comments
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
@abhishek-chouhan@dbwong@gjacoby126 Could you please take a look when you have some bandwidth? |
virajjasani
left a comment
There was a problem hiding this comment.
Left few more comments
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
virajjasani
commented
Jul 19, 2021
@stoty I agree and we have 4.x backport PR #1270 with proper Java 7 semantics so I think we are good with this PR using streams and eventually land on master and 5.1. |
abhishek-chouhan
commented
Jul 19, 2021
I'm not sure if this is a bug. Tenants are allowed to create their own sequences and use those for their operations. In general tenant connections are not able to see data associated with a global non-tenant connection. This could also be considered similar to that. I do think there is value in having a shared sequence across tenants, however need to think more if that should be through enabling it generally, like this pr aims to do, or having something like a "multi-tenant" sequence (create sequnce .. multi-tenant=true). @gjacoby126@virajjasani |
stoty
commented
Jul 19, 2021
💔 -1 overall
This message was automatically generated. |
virajjasani
commented
Jul 20, 2021
Nice one, yeah if not the global sequence, maybe a special type of multi-tenant sequence (i.e new attribute attached to sequence) that can make it accessible to all tenants. |
abhishek-chouhan
commented
Jul 20, 2021
Lets repurpose/open a new jira, which introduces multi-tenant sequences unless there are objections. |
gjacoby126
commented
Jul 21, 2021
@abhishek-chouhan@virajjasani - I believe the usual pattern in Phoenix is that a tenant connection should already be able to see global things. For example, if you get a tenant connection and query a non-MT table, you should be able to get rows back. Tenant connections afaik just add "WHERE [TenantId Column] = [Your connection's tenantId]" to all multi-tenant tables. |
lokiore
commented
Jul 24, 2021
@gjacoby126@abhishek-chouhan@virajjasani - What you guys think should be next steps for this!? |
virajjasani
commented
Jul 27, 2021
Tenant connection can read from global views as well. I think this approach also would be good enough i.e having global sequence accessible to tenant connection. If we are good to go with this approach, changes look good to me per my previous reviews. I was just curious about the final decision on the approach we decide to go ahead with. |
abhishek-chouhan
commented
Jul 27, 2021
Makes sense. Should be fine to go ahead with this since it gives us parity with the current behavior as @gjacoby126 rightly pointed out. |
virajjasani
commented
Jul 28, 2021
Sounds good. Thanks @abhishek-chouhan@gjacoby126 for your valuable inputs. |
…l Sequences (#1261) Signed-off-by: Viraj Jasani <vjasani@apache.org>
No description provided.