[GitHub] [phoenix-omid] chia7712 edited a comment on pull request #80: OMID-188 Fix "inconsistent module metadata found" when using hbase-2
chia7712 edited a comment on pull request #80: URL: https://github.com/apache/phoenix-omid/pull/80#issuecomment-728748262 > but I'll need to test this with Phoenix. thanks for the testing! Some artifact has postfix (hbase-x) now so it may break some dependency rules of downstream. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [phoenix-omid] chia7712 commented on pull request #80: OMID-188 Fix "inconsistent module metadata found" when using hbase-2
chia7712 commented on pull request #80: URL: https://github.com/apache/phoenix-omid/pull/80#issuecomment-728748262 > but I'll need to test this with Phoenix. thanks for the testing! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [phoenix-omid] stoty commented on pull request #80: OMID-188 Fix "inconsistent module metadata found" when using hbase-2
stoty commented on pull request #80: URL: https://github.com/apache/phoenix-omid/pull/80#issuecomment-728747718 This looks like a step in the right direction. but I'll need to test this with Phoenix. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (PHOENIX-5601) PHOENIX-5601 Add a new coprocessor for PHOENIX_TTL - PhoenixTTLRegionObserver
[ https://issues.apache.org/jira/browse/PHOENIX-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Isaac updated PHOENIX-5601: - Attachment: (was: PHOENIX-5601.4.x.002.patch) > PHOENIX-5601 Add a new coprocessor for PHOENIX_TTL - PhoenixTTLRegionObserver > - > > Key: PHOENIX-5601 > URL: https://issues.apache.org/jira/browse/PHOENIX-5601 > Project: Phoenix > Issue Type: Sub-task >Affects Versions: 5.1.0, 4.16.0 >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > > * Add a New coprocessor - ViewTTLAware Coprocessor that will intercept > scan/get requests to inject a new ViewTTLAware scanner. > The scanner will - > * Use the row timestamp of the empty column to determine whether row TTL > has expired and mask the rows from underlying query results. > * Use the row timestamp to delete expired rows when DELETE_VIEW_TTL_EXPIRED > flag is present. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6225) fix the dependency issue on the master branch
[ https://issues.apache.org/jira/browse/PHOENIX-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6225. Resolution: Fixed > fix the dependency issue on the master branch > - > > Key: PHOENIX-6225 > URL: https://issues.apache.org/jira/browse/PHOENIX-6225 > Project: Phoenix > Issue Type: Bug >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 5.1.0 > > Attachments: PHOENIX-6225.master.patch > > > The master branch build failed locally because some of files are import > com.google.common instead of phoenix.thirdparty.com.google.common -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6225) fix the dependency issue on the master branch
[ https://issues.apache.org/jira/browse/PHOENIX-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni reassigned PHOENIX-6225: - Assignee: Xinyi Yan > fix the dependency issue on the master branch > - > > Key: PHOENIX-6225 > URL: https://issues.apache.org/jira/browse/PHOENIX-6225 > Project: Phoenix > Issue Type: Bug >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 5.1.0 > > Attachments: PHOENIX-6225.master.patch > > > The master branch build failed locally because some of files are import > com.google.common instead of phoenix.thirdparty.com.google.common -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6225) fix the dependency issue on the master branch
[ https://issues.apache.org/jira/browse/PHOENIX-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6225: -- Issue Type: Bug (was: Improvement) > fix the dependency issue on the master branch > - > > Key: PHOENIX-6225 > URL: https://issues.apache.org/jira/browse/PHOENIX-6225 > Project: Phoenix > Issue Type: Bug >Reporter: Xinyi Yan >Priority: Major > Fix For: 5.1.0 > > Attachments: PHOENIX-6225.master.patch > > > The master branch build failed locally because some of files are import > com.google.common instead of phoenix.thirdparty.com.google.common -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6225) fix the dependency issue on the master branch
[ https://issues.apache.org/jira/browse/PHOENIX-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6225: --- Attachment: PHOENIX-6225.master.patch > fix the dependency issue on the master branch > - > > Key: PHOENIX-6225 > URL: https://issues.apache.org/jira/browse/PHOENIX-6225 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Priority: Major > Fix For: 5.1.0 > > Attachments: PHOENIX-6225.master.patch > > > The master branch build failed locally because some of files are import > com.google.common instead of phoenix.thirdparty.com.google.common -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6225) fix the dependency issue on the master branch
Xinyi Yan created PHOENIX-6225: -- Summary: fix the dependency issue on the master branch Key: PHOENIX-6225 URL: https://issues.apache.org/jira/browse/PHOENIX-6225 Project: Phoenix Issue Type: Improvement Reporter: Xinyi Yan Fix For: 5.1.0 The master branch build failed locally because some of files are import com.google.common instead of phoenix.thirdparty.com.google.common -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5601) PHOENIX-5601 Add a new coprocessor for PHOENIX_TTL - PhoenixTTLRegionObserver
[ https://issues.apache.org/jira/browse/PHOENIX-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Isaac updated PHOENIX-5601: - Summary: PHOENIX-5601 Add a new coprocessor for PHOENIX_TTL - PhoenixTTLRegionObserver (was: Add a new Coprocessor - ViewTTLAware Coprocessor) > PHOENIX-5601 Add a new coprocessor for PHOENIX_TTL - PhoenixTTLRegionObserver > - > > Key: PHOENIX-5601 > URL: https://issues.apache.org/jira/browse/PHOENIX-5601 > Project: Phoenix > Issue Type: Sub-task >Affects Versions: 5.1.0, 4.16.0 >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > > * Add a New coprocessor - ViewTTLAware Coprocessor that will intercept > scan/get requests to inject a new ViewTTLAware scanner. > The scanner will - > * Use the row timestamp of the empty column to determine whether row TTL > has expired and mask the rows from underlying query results. > * Use the row timestamp to delete expired rows when DELETE_VIEW_TTL_EXPIRED > flag is present. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5601) PHOENIX-5601 Add a new coprocessor for PHOENIX_TTL - PhoenixTTLRegionObserver
[ https://issues.apache.org/jira/browse/PHOENIX-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Isaac updated PHOENIX-5601: - Attachment: (was: PHOENIX-5601.4.x.001.patch) > PHOENIX-5601 Add a new coprocessor for PHOENIX_TTL - PhoenixTTLRegionObserver > - > > Key: PHOENIX-5601 > URL: https://issues.apache.org/jira/browse/PHOENIX-5601 > Project: Phoenix > Issue Type: Sub-task >Affects Versions: 5.1.0, 4.16.0 >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > > * Add a New coprocessor - ViewTTLAware Coprocessor that will intercept > scan/get requests to inject a new ViewTTLAware scanner. > The scanner will - > * Use the row timestamp of the empty column to determine whether row TTL > has expired and mask the rows from underlying query results. > * Use the row timestamp to delete expired rows when DELETE_VIEW_TTL_EXPIRED > flag is present. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6220) CREATE INDEX shouldn't ignore IMMUTABLE_STORAGE_SCHEME and COLUMN_ENDCODED_BYTES
[ https://issues.apache.org/jira/browse/PHOENIX-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gokcen Iskender updated PHOENIX-6220: - Attachment: PHOENIX-6220.4.x.003.patch > CREATE INDEX shouldn't ignore IMMUTABLE_STORAGE_SCHEME and > COLUMN_ENDCODED_BYTES > -- > > Key: PHOENIX-6220 > URL: https://issues.apache.org/jira/browse/PHOENIX-6220 > Project: Phoenix > Issue Type: Sub-task >Reporter: Gokcen Iskender >Assignee: Gokcen Iskender >Priority: Major > Attachments: PHOENIX-6220.4.x.001.patch, PHOENIX-6220.4.x.002.patch, > PHOENIX-6220.4.x.003.patch > > > IMMUTABLE_STORAGE_SCHEME and COLUMN_ENCODED_BYTES that is specified in CREATE > INDEX needs to be respected. Today, it is ignored and value is just gotten > from the parent. Parent table can still use ONE_CELL_PER_COLUMN storage > scheme. If the parent table is using COLUMN_ENCODED_BYTES=0 (none), we > recommend using COLUMN_ENCODED_BYTES=2 for the index table by default (can be > overriden) when SINGLE_CELL storage scheme is used. 2-byte column mapping > enables to define 65535 columns which should be enough. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5601) Add a new Coprocessor - ViewTTLAware Coprocessor
[ https://issues.apache.org/jira/browse/PHOENIX-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Isaac updated PHOENIX-5601: - Attachment: (was: PHOENIX-5601.master.008.patch) > Add a new Coprocessor - ViewTTLAware Coprocessor > > > Key: PHOENIX-5601 > URL: https://issues.apache.org/jira/browse/PHOENIX-5601 > Project: Phoenix > Issue Type: Sub-task >Affects Versions: 5.1.0, 4.16.0 >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > > * Add a New coprocessor - ViewTTLAware Coprocessor that will intercept > scan/get requests to inject a new ViewTTLAware scanner. > The scanner will - > * Use the row timestamp of the empty column to determine whether row TTL > has expired and mask the rows from underlying query results. > * Use the row timestamp to delete expired rows when DELETE_VIEW_TTL_EXPIRED > flag is present. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5601) Add a new Coprocessor - ViewTTLAware Coprocessor
[ https://issues.apache.org/jira/browse/PHOENIX-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Isaac updated PHOENIX-5601: - Attachment: (was: PHOENIX-5601.4.x-HBase-1.3.008.patch) > Add a new Coprocessor - ViewTTLAware Coprocessor > > > Key: PHOENIX-5601 > URL: https://issues.apache.org/jira/browse/PHOENIX-5601 > Project: Phoenix > Issue Type: Sub-task >Affects Versions: 5.1.0, 4.16.0 >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > > * Add a New coprocessor - ViewTTLAware Coprocessor that will intercept > scan/get requests to inject a new ViewTTLAware scanner. > The scanner will - > * Use the row timestamp of the empty column to determine whether row TTL > has expired and mask the rows from underlying query results. > * Use the row timestamp to delete expired rows when DELETE_VIEW_TTL_EXPIRED > flag is present. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEPHRA-315) tephra-example maven setup is broken
[ https://issues.apache.org/jira/browse/TEPHRA-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232617#comment-17232617 ] Istvan Toth commented on TEPHRA-315: As this blocks 0.16.0, the fix will have to be backported to the release/0.16.0 branch before we can release 0.16.0 > tephra-example maven setup is broken > > > Key: TEPHRA-315 > URL: https://issues.apache.org/jira/browse/TEPHRA-315 > Project: Phoenix Tephra > Issue Type: Bug >Affects Versions: 0.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Blocker > > I could not deploy the 0.16.0RC0 because mvn deploy fails. > Unfortunately the mvn build fails only on the deploy target, it doesn't fail > on package or install. > The reason is that the example submodules are set up incorrectly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [phoenix-tephra] stoty opened a new pull request #110: TEPHRA-315 tephra-example maven setup is broken
stoty opened a new pull request #110: URL: https://github.com/apache/phoenix-tephra/pull/110 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (TEPHRA-315) tephra-example maven setup is broken
Istvan Toth created TEPHRA-315: -- Summary: tephra-example maven setup is broken Key: TEPHRA-315 URL: https://issues.apache.org/jira/browse/TEPHRA-315 Project: Phoenix Tephra Issue Type: Bug Affects Versions: 0.16.0 Reporter: Istvan Toth Assignee: Istvan Toth I could not deploy the 0.16.0RC0 because mvn deploy fails. Unfortunately the mvn build fails only on the deploy target, it doesn't fail on package or install. The reason is that the example submodules are set up incorrectly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
