[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maddineni Sukumar updated PHOENIX-2885: --- Attachment: PHOENIX-2885.v3.patch > Set default value for UPDATE_CACHE_FREQUENCY > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Sub-task >Reporter: James Taylor >Assignee: Maddineni Sukumar > Fix For: 4.11.0 > > Attachments: PHOENIX-2885.4.10-HBase-0.98.patch, > PHOENIX-2885.v2.patch, PHOENIX-2885.v3.patch > > > We have the ability currently to tell Phoenix how stale we're will to have > the metadata through our UPDATE_CACHE_FREQUENCY feature[1]. By default, when > a table is created, unless explicitly specified, there is no > UPDATE_CACHE_FREQUENCY set. We should provide a new Phoenix configuration > parameter to specify a default value when a CREATE TABLE statement is > executed. In addition, when a VIEW is created, we should inherit the > UPDATE_CACHE_FREQUENCY value from the parent (unless it's explicitly > specified) and then fallback to the new default config value. > [1] https://phoenix.apache.org/language/index.html#options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maddineni Sukumar updated PHOENIX-2885: --- Attachment: PHOENIX-2885.v2.patch > Set default value for UPDATE_CACHE_FREQUENCY > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Sub-task >Reporter: James Taylor >Assignee: Maddineni Sukumar > Fix For: 4.11.0 > > Attachments: PHOENIX-2885.4.10-HBase-0.98.patch, PHOENIX-2885.v2.patch > > > We have the ability currently to tell Phoenix how stale we're will to have > the metadata through our UPDATE_CACHE_FREQUENCY feature[1]. By default, when > a table is created, unless explicitly specified, there is no > UPDATE_CACHE_FREQUENCY set. We should provide a new Phoenix configuration > parameter to specify a default value when a CREATE TABLE statement is > executed. In addition, when a VIEW is created, we should inherit the > UPDATE_CACHE_FREQUENCY value from the parent (unless it's explicitly > specified) and then fallback to the new default config value. > [1] https://phoenix.apache.org/language/index.html#options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maddineni Sukumar updated PHOENIX-2885: --- Attachment: PHOENIX-2885.4.10-HBase-0.98.patch > Set default value for UPDATE_CACHE_FREQUENCY > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Sub-task >Reporter: James Taylor >Assignee: Maddineni Sukumar > Fix For: 4.11.0 > > Attachments: PHOENIX-2885.4.10-HBase-0.98.patch > > > We have the ability currently to tell Phoenix how stale we're will to have > the metadata through our UPDATE_CACHE_FREQUENCY feature[1]. By default, when > a table is created, unless explicitly specified, there is no > UPDATE_CACHE_FREQUENCY set. We should provide a new Phoenix configuration > parameter to specify a default value when a CREATE TABLE statement is > executed. In addition, when a VIEW is created, we should inherit the > UPDATE_CACHE_FREQUENCY value from the parent (unless it's explicitly > specified) and then fallback to the new default config value. > [1] https://phoenix.apache.org/language/index.html#options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maddineni Sukumar updated PHOENIX-2885: --- Attachment: PHOENIX-2885.v1.patch > Set default value for UPDATE_CACHE_FREQUENCY > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Sub-task >Reporter: James Taylor >Assignee: Maddineni Sukumar > Fix For: 4.11.0 > > > We have the ability currently to tell Phoenix how stale we're will to have > the metadata through our UPDATE_CACHE_FREQUENCY feature[1]. By default, when > a table is created, unless explicitly specified, there is no > UPDATE_CACHE_FREQUENCY set. We should provide a new Phoenix configuration > parameter to specify a default value when a CREATE TABLE statement is > executed. In addition, when a VIEW is created, we should inherit the > UPDATE_CACHE_FREQUENCY value from the parent (unless it's explicitly > specified) and then fallback to the new default config value. > [1] https://phoenix.apache.org/language/index.html#options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maddineni Sukumar updated PHOENIX-2885: --- Attachment: (was: PHOENIX-2885.v1.patch) > Set default value for UPDATE_CACHE_FREQUENCY > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Sub-task >Reporter: James Taylor >Assignee: Maddineni Sukumar > Fix For: 4.11.0 > > > We have the ability currently to tell Phoenix how stale we're will to have > the metadata through our UPDATE_CACHE_FREQUENCY feature[1]. By default, when > a table is created, unless explicitly specified, there is no > UPDATE_CACHE_FREQUENCY set. We should provide a new Phoenix configuration > parameter to specify a default value when a CREATE TABLE statement is > executed. In addition, when a VIEW is created, we should inherit the > UPDATE_CACHE_FREQUENCY value from the parent (unless it's explicitly > specified) and then fallback to the new default config value. > [1] https://phoenix.apache.org/language/index.html#options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Description: We have the ability currently to tell Phoenix how stale we're will to have the metadata through our UPDATE_CACHE_FREQUENCY feature[1]. By default, when a table is created, unless explicitly specified, there is no UPDATE_CACHE_FREQUENCY set. We should provide a new Phoenix configuration parameter to specify a default value when a CREATE TABLE statement is executed. In addition, when a VIEW is created, we should inherit the UPDATE_CACHE_FREQUENCY value from the parent (unless it's explicitly specified) and then fallback to the new default config value. [1] https://phoenix.apache.org/language/index.html#options was:Instead of by default doing an extra RPC per query, we should have a default value for UPDATE_CACHE_FREQUENCY. Instead of throwing when an entity (table/column/column family, etc) is not found, we can force an update of the client-side cache and retry the statement once. This works well for references to entities that don't yet exist. However, we won't detect when some entities are referred to which no longer exists until the cache expires. An exception is if a physical table is dropped which would be detected immediately. Worst-case, we may allow queries and updates to columns which have been dropped. In addition, we won't start using indexes on tables until the cache expires. > Set default value for UPDATE_CACHE_FREQUENCY > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Sub-task >Reporter: James Taylor >Assignee: Maddineni Sukumar > Fix For: 4.11.0 > > > We have the ability currently to tell Phoenix how stale we're will to have > the metadata through our UPDATE_CACHE_FREQUENCY feature[1]. By default, when > a table is created, unless explicitly specified, there is no > UPDATE_CACHE_FREQUENCY set. We should provide a new Phoenix configuration > parameter to specify a default value when a CREATE TABLE statement is > executed. In addition, when a VIEW is created, we should inherit the > UPDATE_CACHE_FREQUENCY value from the parent (unless it's explicitly > specified) and then fallback to the new default config value. > [1] https://phoenix.apache.org/language/index.html#options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Issue Type: Sub-task (was: Bug) Parent: PHOENIX-3819 > Set default value for UPDATE_CACHE_FREQUENCY > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Sub-task >Reporter: James Taylor >Assignee: Maddineni Sukumar > Fix For: 4.11.0 > > > Instead of by default doing an extra RPC per query, we should have a default > value for UPDATE_CACHE_FREQUENCY. Instead of throwing when an entity > (table/column/column family, etc) is not found, we can force an update of the > client-side cache and retry the statement once. This works well for > references to entities that don't yet exist. However, we won't detect when > some entities are referred to which no longer exists until the cache expires. > An exception is if a physical table is dropped which would be detected > immediately. Worst-case, we may allow queries and updates to columns which > have been dropped. In addition, we won't start using indexes on tables until > the cache expires. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Summary: Set default value for UPDATE_CACHE_FREQUENCY (was: Set default value for UPDATE_CACHE_FREQUENCY and handle not found exceptions) > Set default value for UPDATE_CACHE_FREQUENCY > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Bug >Reporter: James Taylor >Assignee: Maddineni Sukumar > Fix For: 4.11.0 > > > Instead of by default doing an extra RPC per query, we should have a default > value for UPDATE_CACHE_FREQUENCY. Instead of throwing when an entity > (table/column/column family, etc) is not found, we can force an update of the > client-side cache and retry the statement once. This works well for > references to entities that don't yet exist. However, we won't detect when > some entities are referred to which no longer exists until the cache expires. > An exception is if a physical table is dropped which would be detected > immediately. Worst-case, we may allow queries and updates to columns which > have been dropped. In addition, we won't start using indexes on tables until > the cache expires. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY and handle not found exceptions
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Summary: Set default value for UPDATE_CACHE_FREQUENCY and handle not found exceptions (was: Set default value for UPDATE_CACHE_FREQUENCY) > Set default value for UPDATE_CACHE_FREQUENCY and handle not found exceptions > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Bug >Reporter: James Taylor > Fix For: 4.11.0 > > > Instead of by default doing an extra RPC per query, we should have a default > value for UPDATE_CACHE_FREQUENCY. Instead of throwing when an entity > (table/column/column family, etc) is not found, we can force an update of the > client-side cache and retry the statement once. This works well for > references to entities that don't yet exist. However, we won't detect when > some entities are referred to which no longer exists until the cache expires. > An exception is if a physical table is dropped which would be detected > immediately. Worst-case, we may allow queries and updates to columns which > have been dropped. In addition, we won't start using indexes on tables until > the cache expires. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Description: Instead of by default doing an extra RPC per query, we should have a default value for UPDATE_CACHE_FREQUENCY. Instead of throwing when an entity (table/column/column family, etc) is not found, we can force an update of the client-side cache and retry the statement once. This works well for references to entities that don't yet exist. However, we won't detect when some entities are referred to which no longer exists until the cache expires. An exception is if a physical table is dropped which would be detected immediately. Worst-case, we may allow queries and updates to columns which have been dropped. In addition, we won't start using indexes on tables until the cache expires. (was: Instead of by default doing an extra RPC per query, we should have a default value for UPDATE_CACHE_FREQUENCY. Instead of throwing when an entity (table/column/column family, etc) is not found, we can force an update of the client-side cache and retry the statement once. This works well for references to entities that don't yet exist. However, we won't detect when some entities are referred to which no longer exists until the cache expires. An exception is if a physical table is dropped which would be detected immediately. In addition, we won't start using indexes on tables until the cache expires.) > Set default value for UPDATE_CACHE_FREQUENCY > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Bug >Reporter: James Taylor > Fix For: 4.9.0 > > > Instead of by default doing an extra RPC per query, we should have a default > value for UPDATE_CACHE_FREQUENCY. Instead of throwing when an entity > (table/column/column family, etc) is not found, we can force an update of the > client-side cache and retry the statement once. This works well for > references to entities that don't yet exist. However, we won't detect when > some entities are referred to which no longer exists until the cache expires. > An exception is if a physical table is dropped which would be detected > immediately. Worst-case, we may allow queries and updates to columns which > have been dropped. In addition, we won't start using indexes on tables until > the cache expires. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Description: Instead of by default doing an extra RPC per query, we should have a default value for UPDATE_CACHE_FREQUENCY. Instead of throwing when an entity (table/column/column family, etc) is not found, we can force an update of the client-side cache and retry the statement once. This works well for references to entities that don't yet exist. However, we won't detect when some entities are referred to which no longer exists until the cache expires. An exception is if a physical table is dropped which would be detected immediately. In addition, we won't start using indexes on tables until the cache expires. (was: Instead of by default doing an extra RPC per query, we should have a default value for With the increased usage of the UPDATE_CACHE_FREQUENCY property to reduce RPCs, we increase the chance that a separate client attempts to access a column that doesn't exist on the cached entity. Instead of throwing in this case, we can update the client-side cache. This works well for references to entities (columns, tables) that don't yet exist. For entities that *do* exist, we won't detect that they've been deleted.) > Set default value for UPDATE_CACHE_FREQUENCY > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Bug >Reporter: James Taylor > Fix For: 4.9.0 > > > Instead of by default doing an extra RPC per query, we should have a default > value for UPDATE_CACHE_FREQUENCY. Instead of throwing when an entity > (table/column/column family, etc) is not found, we can force an update of the > client-side cache and retry the statement once. This works well for > references to entities that don't yet exist. However, we won't detect when > some entities are referred to which no longer exists until the cache expires. > An exception is if a physical table is dropped which would be detected > immediately. In addition, we won't start using indexes on tables until the > cache expires. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Description: Instead of by default doing an extra RPC per query, we should have a default value for With the increased usage of the UPDATE_CACHE_FREQUENCY property to reduce RPCs, we increase the chance that a separate client attempts to access a column that doesn't exist on the cached entity. Instead of throwing in this case, we can update the client-side cache. This works well for references to entities (columns, tables) that don't yet exist. For entities that *do* exist, we won't detect that they've been deleted. (was: With the increased usage of the UPDATE_CACHE_FREQUENCY property to reduce RPCs, we increase the chance that a separate client attempts to access a column that doesn't exist on the cached entity. Instead of throwing in this case, we can update the client-side cache. This works well for references to entities (columns, tables) that don't yet exist. For entities that *do* exist, we won't detect that they've been deleted.) > Set default value for UPDATE_CACHE_FREQUENCY > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Bug >Reporter: James Taylor > Fix For: 4.9.0 > > > Instead of by default doing an extra RPC per query, we should have a default > value for With the increased usage of the UPDATE_CACHE_FREQUENCY property to > reduce RPCs, we increase the chance that a separate client attempts to access > a column that doesn't exist on the cached entity. Instead of throwing in this > case, we can update the client-side cache. This works well for references to > entities (columns, tables) that don't yet exist. For entities that *do* > exist, we won't detect that they've been deleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PHOENIX-2885) Set default value for UPDATE_CACHE_FREQUENCY
[ https://issues.apache.org/jira/browse/PHOENIX-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2885: -- Summary: Set default value for UPDATE_CACHE_FREQUENCY (was: Refresh client side cache before throwing not found exception) > Set default value for UPDATE_CACHE_FREQUENCY > > > Key: PHOENIX-2885 > URL: https://issues.apache.org/jira/browse/PHOENIX-2885 > Project: Phoenix > Issue Type: Bug >Reporter: James Taylor > Fix For: 4.9.0 > > > With the increased usage of the UPDATE_CACHE_FREQUENCY property to reduce > RPCs, we increase the chance that a separate client attempts to access a > column that doesn't exist on the cached entity. Instead of throwing in this > case, we can update the client-side cache. This works well for references to > entities (columns, tables) that don't yet exist. For entities that *do* > exist, we won't detect that they've been deleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
