[jira] [Updated] (PHOENIX-5147) Add an option to disable spooling ( SORT MERGE strategy in QueryCompiler )
[ https://issues.apache.org/jira/browse/PHOENIX-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xu Cang updated PHOENIX-5147: - Attachment: PHOENIX-5147.4.x-HBase-1.3.003.patch > Add an option to disable spooling ( SORT MERGE strategy in QueryCompiler ) > -- > > Key: PHOENIX-5147 > URL: https://issues.apache.org/jira/browse/PHOENIX-5147 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Xu Cang >Assignee: Xu Cang >Priority: Major > Attachments: PHOENIX-5147.4.x-HBase-1.3.001.patch, > PHOENIX-5147.4.x-HBase-1.3.002.patch, PHOENIX-5147.4.x-HBase-1.3.003.patch > > > We should add an option to allow database admin to disable using spooling > from the server side. > Especially before PHOENIX-5135 is fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (PHOENIX-5155) Phoenix treats ENCRYPTION and ENCRYPTION_KEY as TableDescriptor
Miles Spielberg created PHOENIX-5155: Summary: Phoenix treats ENCRYPTION and ENCRYPTION_KEY as TableDescriptor Key: PHOENIX-5155 URL: https://issues.apache.org/jira/browse/PHOENIX-5155 Project: Phoenix Issue Type: Bug Reporter: Miles Spielberg As described in the code ([https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java#L1187|https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java#L1187)]), Phoenix uses a "somewhat hacky way" of determining if a table property should be set on an HTableDescriptor or on the HColumnDescriptors for each column family. It does this by checking if an otherwise unconfigured HColumnDescriptor has a default value for the specified property. This mostly works, but the two exceptions as of HBase 1.4 are ENCRYPTION and ENCRYPTION_KEY, which are HColumnDescriptor properties, but have no default values ([https://github.com/apache/hbase/blob/rel/1.4.9/hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java#L245|https://github.com/apache/hbase/blob/rel/1.4.9/hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java#L245).]). As a result, Phoenix incorrectly sets ENCRYPTION on the HTableDescriptor, where it has no effect. Current HBase master has added additional properties that also have no default values: ([https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ColumnFamilyDescriptorBuilder.java#L285|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ColumnFamilyDescriptorBuilder.java#L285)]) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (PHOENIX-5019) Index mutations created by synchronous index builds will have wrong timestamps
[ https://issues.apache.org/jira/browse/PHOENIX-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kadir OZDEMIR resolved PHOENIX-5019. Resolution: Resolved Changing the state to resolved as the patch for PHOENIX-5018 fixes this issue too. > Index mutations created by synchronous index builds will have wrong timestamps > -- > > Key: PHOENIX-5019 > URL: https://issues.apache.org/jira/browse/PHOENIX-5019 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.14.1 >Reporter: Vincent Poon >Assignee: Kadir OZDEMIR >Priority: Major > > Similar to PHOENIX-5018, if we do a synchronous index build, since it's doing > an UpsertSelect , the timestamp of an index mutation will have current > wallclock time instead matching up with the data table counterpart's timestamp -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (PHOENIX-5118) Index Maintainer writes a wrong value to the empty column
[
https://issues.apache.org/jira/browse/PHOENIX-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kadir OZDEMIR resolved PHOENIX-5118.
Resolution: Resolved
Changing the state to resolved as the patch for PHOENIX-5018 fixes this issue
too.
> Index Maintainer writes a wrong value to the empty column
> -
>
> Key: PHOENIX-5118
> URL: https://issues.apache.org/jira/browse/PHOENIX-5118
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Kadir OZDEMIR
>Assignee: Kadir OZDEMIR
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Index Maintainer writes the name of the empty key column qualifier (("_0")
> instead of the predefined value (i.e., "x") to the the empty key column. This
> unnecessarily increases the length of each row by tree bytes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
