[jira] [Assigned] (OMID-283) Support for build on mac M1
[
https://issues.apache.org/jira/browse/OMID-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth reassigned OMID-283:
Assignee: Nikita Pande
> Support for build on mac M1
> ---
>
> Key: OMID-283
> URL: https://issues.apache.org/jira/browse/OMID-283
> Project: Phoenix Omid
> Issue Type: Improvement
>Reporter: Nikita Pande
>Assignee: Nikita Pande
>Priority: Major
>
> * Current code throws following error in `mvn install` command on mac M1
> *
> {noformat}
> [ERROR] Failed to execute goal
> org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:compile
> (compile-protoc) on project omid-common: Configuration error: Invalid
> artifact specification format, expected:
> groupId:artifactId:version[:type[:classifier]], actual:
> com.google.protobuf:protoc:osx-aarch_64:2.5.0:exe:osx-aarch_64 -> [Help
> 1]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OMID-283) Support for build on mac M1
[
https://issues.apache.org/jira/browse/OMID-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823467#comment-17823467
]
Istvan Toth commented on OMID-283:
--
I have added [~nikitapande] as a contributor to Omid.
> Support for build on mac M1
> ---
>
> Key: OMID-283
> URL: https://issues.apache.org/jira/browse/OMID-283
> Project: Phoenix Omid
> Issue Type: Improvement
>Reporter: Nikita Pande
>Priority: Major
>
> * Current code throws following error in `mvn install` command on mac M1
> *
> {noformat}
> [ERROR] Failed to execute goal
> org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:compile
> (compile-protoc) on project omid-common: Configuration error: Invalid
> artifact specification format, expected:
> groupId:artifactId:version[:type[:classifier]], actual:
> com.google.protobuf:protoc:osx-aarch_64:2.5.0:exe:osx-aarch_64 -> [Help
> 1]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OMID-283) Support for build on mac M1
[
https://issues.apache.org/jira/browse/OMID-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823465#comment-17823465
]
ASF GitHub Bot commented on OMID-283:
-
stoty commented on PR #159:
URL: https://github.com/apache/phoenix-omid/pull/159#issuecomment-1978119830
I will not commit this now, as @chrajeshbabu is in the middle of creating a
release, and I don't want to interfere.
> Support for build on mac M1
> ---
>
> Key: OMID-283
> URL: https://issues.apache.org/jira/browse/OMID-283
> Project: Phoenix Omid
> Issue Type: Improvement
>Reporter: Nikita Pande
>Priority: Major
>
> * Current code throws following error in `mvn install` command on mac M1
> *
> {noformat}
> [ERROR] Failed to execute goal
> org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:compile
> (compile-protoc) on project omid-common: Configuration error: Invalid
> artifact specification format, expected:
> groupId:artifactId:version[:type[:classifier]], actual:
> com.google.protobuf:protoc:osx-aarch_64:2.5.0:exe:osx-aarch_64 -> [Help
> 1]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (PHOENIX-7253) Perf improvement for non-full scan queries on large table
[
https://issues.apache.org/jira/browse/PHOENIX-7253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated PHOENIX-7253:
--
Fix Version/s: 5.2.0
5.1.4
> Perf improvement for non-full scan queries on large table
> -
>
> Key: PHOENIX-7253
> URL: https://issues.apache.org/jira/browse/PHOENIX-7253
> Project: Phoenix
> Issue Type: Improvement
>Affects Versions: 5.2.0, 5.1.3
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Critical
> Fix For: 5.2.0, 5.1.4
>
>
> Any considerably large table with more than 100k regions can give problematic
> performance if we access all region locations from meta for the given table
> before generating parallel or sequential scans for the given query. The perf
> impact can really hurt range scan queries.
> Consider a table with hundreds of thousands of tenant views. Unless the query
> is strict point lookup, any query on any tenant view would end up retrieving
> region locations of all regions of the base table. In case if IOException is
> thrown by HBase client during any region location lookup in meta, we only
> perform single retry.
> Proposal:
> # All non point lookup queries should only retrieve region locations that
> cover the scan boundary. Avoid fetching all region locations of the base
> table.
> # Make retries configurable with higher default value.
>
> Sample stacktrace from the multiple failures observed:
> {code:java}
> java.sql.SQLException: ERROR 1102 (XCL02): Cannot get all table regions.Stack
> trace: java.sql.SQLException: ERROR 1102 (XCL02): Cannot get all table
> regions.
> at
> org.apache.phoenix.exception.SQLExceptionCode$Factory$1.newException(SQLExceptionCode.java:620)
> at
> org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:229)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl.getAllTableRegions(ConnectionQueryServicesImpl.java:781)
> at
> org.apache.phoenix.query.DelegateConnectionQueryServices.getAllTableRegions(DelegateConnectionQueryServices.java:87)
> at
> org.apache.phoenix.query.DelegateConnectionQueryServices.getAllTableRegions(DelegateConnectionQueryServices.java:87)
> at
> org.apache.phoenix.iterate.DefaultParallelScanGrouper.getRegionBoundaries(DefaultParallelScanGrouper.java:74)
> at
> org.apache.phoenix.iterate.BaseResultIterators.getRegionBoundaries(BaseResultIterators.java:587)
> at
> org.apache.phoenix.iterate.BaseResultIterators.getParallelScans(BaseResultIterators.java:936)
> at
> org.apache.phoenix.iterate.BaseResultIterators.getParallelScans(BaseResultIterators.java:669)
> at
> org.apache.phoenix.iterate.BaseResultIterators.(BaseResultIterators.java:555)
> at
> org.apache.phoenix.iterate.SerialIterators.(SerialIterators.java:69)
> at org.apache.phoenix.execute.ScanPlan.newIterator(ScanPlan.java:278)
> at
> org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:374)
> at
> org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:222)
> at
> org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:217)
> at
> org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:212)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:370)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:328)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:328)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:320)
> at
> org.apache.phoenix.jdbc.PhoenixPreparedStatement.executeQuery(PhoenixPreparedStatement.java:188)
> ...
> ...
> Caused by: java.io.InterruptedIOException: Origin: InterruptedException
> at
> org.apache.hadoop.hbase.util.ExceptionUtil.asInterrupt(ExceptionUtil.java:72)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.takeUserRegionLock(ConnectionImplementation.java:1129)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegionInMeta(ConnectionImplementation.java:994)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:895)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:881)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:851)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.getRegionLocation(ConnectionImplementation.java:730)
> at
>
[jira] [Commented] (OMID-285) Enable build pipelines for Omid
[ https://issues.apache.org/jira/browse/OMID-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823456#comment-17823456 ] Istvan Toth commented on OMID-285: -- We could also check to see what it would take to get Travis working again (do they still have some kind of open source scheme) But I think it's easier to just use Github actions, as the old travis were just a simple version matrix maven test runners. (And we have a far simpler setup without the old HBase support now) > Enable build pipelines for Omid > --- > > Key: OMID-285 > URL: https://issues.apache.org/jira/browse/OMID-285 > Project: Phoenix Omid > Issue Type: Task >Reporter: Rajeshbabu Chintaguntla >Assignee: Rajeshbabu Chintaguntla >Priority: Major > > Currently no pipelines for Omid. > Would be better to have both precommit and nightlies. > FYI [~stoty] [~nihaljain.cs] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (PHOENIX-7253) Perf improvement for non-full scan queries on large table
Viraj Jasani created PHOENIX-7253:
-
Summary: Perf improvement for non-full scan queries on large table
Key: PHOENIX-7253
URL: https://issues.apache.org/jira/browse/PHOENIX-7253
Project: Phoenix
Issue Type: Improvement
Affects Versions: 5.1.3, 5.2.0
Reporter: Viraj Jasani
Any considerably large table with more than 100k regions can give problematic
performance if we access all region locations from meta for the given table
before generating parallel or sequential scans for the given query. The perf
impact can really hurt range scan queries.
Consider a table with hundreds of thousands of tenant views. Unless the query
is strict point lookup, any query on any tenant view would end up retrieving
region locations of all regions of the base table. In case if IOException is
thrown by HBase client during any region location lookup in meta, we only
perform single retry.
Proposal:
# All non point lookup queries should only retrieve region locations that
cover the scan boundary. Avoid fetching all region locations of the base table.
# Make retries configurable with higher default value.
Sample stacktrace from the multiple failures observed:
{code:java}
java.sql.SQLException: ERROR 1102 (XCL02): Cannot get all table regions.Stack
trace: java.sql.SQLException: ERROR 1102 (XCL02): Cannot get all table regions.
at
org.apache.phoenix.exception.SQLExceptionCode$Factory$1.newException(SQLExceptionCode.java:620)
at
org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:229)
at
org.apache.phoenix.query.ConnectionQueryServicesImpl.getAllTableRegions(ConnectionQueryServicesImpl.java:781)
at
org.apache.phoenix.query.DelegateConnectionQueryServices.getAllTableRegions(DelegateConnectionQueryServices.java:87)
at
org.apache.phoenix.query.DelegateConnectionQueryServices.getAllTableRegions(DelegateConnectionQueryServices.java:87)
at
org.apache.phoenix.iterate.DefaultParallelScanGrouper.getRegionBoundaries(DefaultParallelScanGrouper.java:74)
at
org.apache.phoenix.iterate.BaseResultIterators.getRegionBoundaries(BaseResultIterators.java:587)
at
org.apache.phoenix.iterate.BaseResultIterators.getParallelScans(BaseResultIterators.java:936)
at
org.apache.phoenix.iterate.BaseResultIterators.getParallelScans(BaseResultIterators.java:669)
at
org.apache.phoenix.iterate.BaseResultIterators.(BaseResultIterators.java:555)
at
org.apache.phoenix.iterate.SerialIterators.(SerialIterators.java:69)
at org.apache.phoenix.execute.ScanPlan.newIterator(ScanPlan.java:278)
at org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:374)
at org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:222)
at org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:217)
at org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:212)
at
org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:370)
at
org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:328)
at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
at
org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:328)
at
org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:320)
at
org.apache.phoenix.jdbc.PhoenixPreparedStatement.executeQuery(PhoenixPreparedStatement.java:188)
...
...
Caused by: java.io.InterruptedIOException: Origin: InterruptedException
at
org.apache.hadoop.hbase.util.ExceptionUtil.asInterrupt(ExceptionUtil.java:72)
at
org.apache.hadoop.hbase.client.ConnectionImplementation.takeUserRegionLock(ConnectionImplementation.java:1129)
at
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegionInMeta(ConnectionImplementation.java:994)
at
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:895)
at
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:881)
at
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:851)
at
org.apache.hadoop.hbase.client.ConnectionImplementation.getRegionLocation(ConnectionImplementation.java:730)
at
org.apache.phoenix.query.ConnectionQueryServicesImpl.getAllTableRegions(ConnectionQueryServicesImpl.java:766)
... 254 more
Caused by: java.lang.InterruptedException
at
java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireNanos(AbstractQueuedSynchronizer.java:982)
at
java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireNanos(AbstractQueuedSynchronizer.java:1288)
at
java.base/java.util.concurrent.locks.ReentrantLock.tryLock(ReentrantLock.java:424)
at
[jira] [Assigned] (PHOENIX-7253) Perf improvement for non-full scan queries on large table
[
https://issues.apache.org/jira/browse/PHOENIX-7253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned PHOENIX-7253:
-
Assignee: Viraj Jasani
> Perf improvement for non-full scan queries on large table
> -
>
> Key: PHOENIX-7253
> URL: https://issues.apache.org/jira/browse/PHOENIX-7253
> Project: Phoenix
> Issue Type: Improvement
>Affects Versions: 5.2.0, 5.1.3
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Critical
>
> Any considerably large table with more than 100k regions can give problematic
> performance if we access all region locations from meta for the given table
> before generating parallel or sequential scans for the given query. The perf
> impact can really hurt range scan queries.
> Consider a table with hundreds of thousands of tenant views. Unless the query
> is strict point lookup, any query on any tenant view would end up retrieving
> region locations of all regions of the base table. In case if IOException is
> thrown by HBase client during any region location lookup in meta, we only
> perform single retry.
> Proposal:
> # All non point lookup queries should only retrieve region locations that
> cover the scan boundary. Avoid fetching all region locations of the base
> table.
> # Make retries configurable with higher default value.
>
> Sample stacktrace from the multiple failures observed:
> {code:java}
> java.sql.SQLException: ERROR 1102 (XCL02): Cannot get all table regions.Stack
> trace: java.sql.SQLException: ERROR 1102 (XCL02): Cannot get all table
> regions.
> at
> org.apache.phoenix.exception.SQLExceptionCode$Factory$1.newException(SQLExceptionCode.java:620)
> at
> org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:229)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl.getAllTableRegions(ConnectionQueryServicesImpl.java:781)
> at
> org.apache.phoenix.query.DelegateConnectionQueryServices.getAllTableRegions(DelegateConnectionQueryServices.java:87)
> at
> org.apache.phoenix.query.DelegateConnectionQueryServices.getAllTableRegions(DelegateConnectionQueryServices.java:87)
> at
> org.apache.phoenix.iterate.DefaultParallelScanGrouper.getRegionBoundaries(DefaultParallelScanGrouper.java:74)
> at
> org.apache.phoenix.iterate.BaseResultIterators.getRegionBoundaries(BaseResultIterators.java:587)
> at
> org.apache.phoenix.iterate.BaseResultIterators.getParallelScans(BaseResultIterators.java:936)
> at
> org.apache.phoenix.iterate.BaseResultIterators.getParallelScans(BaseResultIterators.java:669)
> at
> org.apache.phoenix.iterate.BaseResultIterators.(BaseResultIterators.java:555)
> at
> org.apache.phoenix.iterate.SerialIterators.(SerialIterators.java:69)
> at org.apache.phoenix.execute.ScanPlan.newIterator(ScanPlan.java:278)
> at
> org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:374)
> at
> org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:222)
> at
> org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:217)
> at
> org.apache.phoenix.execute.BaseQueryPlan.iterator(BaseQueryPlan.java:212)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:370)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:328)
> at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:328)
> at
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:320)
> at
> org.apache.phoenix.jdbc.PhoenixPreparedStatement.executeQuery(PhoenixPreparedStatement.java:188)
> ...
> ...
> Caused by: java.io.InterruptedIOException: Origin: InterruptedException
> at
> org.apache.hadoop.hbase.util.ExceptionUtil.asInterrupt(ExceptionUtil.java:72)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.takeUserRegionLock(ConnectionImplementation.java:1129)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegionInMeta(ConnectionImplementation.java:994)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:895)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:881)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:851)
> at
> org.apache.hadoop.hbase.client.ConnectionImplementation.getRegionLocation(ConnectionImplementation.java:730)
> at
> org.apache.phoenix.query.ConnectionQueryServicesImpl.getAllTableRegions(ConnectionQueryServicesImpl.java:766)
>
[jira] [Comment Edited] (OMID-285) Enable build pipelines for Omid
[ https://issues.apache.org/jira/browse/OMID-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823454#comment-17823454 ] Istvan Toth edited comment on OMID-285 at 3/5/24 7:02 AM: -- The better but harder way is to adapt Yetus and use the ASF infra. The quick and dirty way is to add a simple Github actions based check. (I think GH actions can only do precommits) was (Author: stoty): The better but harder way is to adapt Yetus and use the ASF infra. The quick and dirty way is to add a simple Github actions based check. > Enable build pipelines for Omid > --- > > Key: OMID-285 > URL: https://issues.apache.org/jira/browse/OMID-285 > Project: Phoenix Omid > Issue Type: Task >Reporter: Rajeshbabu Chintaguntla >Assignee: Rajeshbabu Chintaguntla >Priority: Major > > Currently no pipelines for Omid. > Would be better to have both precommit and nightlies. > FYI [~stoty] [~nihaljain.cs] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OMID-285) Enable build pipelines for Omid
[ https://issues.apache.org/jira/browse/OMID-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823454#comment-17823454 ] Istvan Toth commented on OMID-285: -- The better but harder way is to adapt Yetus and use the ASF infra. The quick and dirty way is to add a simple Github actions based check. > Enable build pipelines for Omid > --- > > Key: OMID-285 > URL: https://issues.apache.org/jira/browse/OMID-285 > Project: Phoenix Omid > Issue Type: Task >Reporter: Rajeshbabu Chintaguntla >Assignee: Rajeshbabu Chintaguntla >Priority: Major > > Currently no pipelines for Omid. > Would be better to have both precommit and nightlies. > FYI [~stoty] [~nihaljain.cs] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OMID-285) Enable build pipelines for Omid
Rajeshbabu Chintaguntla created OMID-285: Summary: Enable build pipelines for Omid Key: OMID-285 URL: https://issues.apache.org/jira/browse/OMID-285 Project: Phoenix Omid Issue Type: Task Reporter: Rajeshbabu Chintaguntla Assignee: Rajeshbabu Chintaguntla Currently no pipelines for Omid. Would be better to have both precommit and nightlies. FYI [~stoty] [~nihaljain.cs] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OMID-284) Use protobuf 3 in Omid
[ https://issues.apache.org/jira/browse/OMID-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823452#comment-17823452 ] Rajeshbabu Chintaguntla commented on OMID-284: -- Agree with you [~stoty] . Better to bump up. > Use protobuf 3 in Omid > -- > > Key: OMID-284 > URL: https://issues.apache.org/jira/browse/OMID-284 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.1.2 >Reporter: Istvan Toth >Priority: Critical > > Omid uses Protobuf 2.5.0. > It only uses protobuf for communicating with the TSO server, it does not > implement an HBase endpoint, so I see no reason not to use the latest version. > This could be done in 1.2, provided that the switch does not cause > compatibility issues (I expect none) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-7249) Starting HTTP Server with Python3 For website validation fails with error No module named SimpleHTTPServer
[
https://issues.apache.org/jira/browse/PHOENIX-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anchal Kejriwal updated PHOENIX-7249:
-
Attachment: phoenix-website-1.patch
> Starting HTTP Server with Python3 For website validation fails with error No
> module named SimpleHTTPServer
> ---
>
> Key: PHOENIX-7249
> URL: https://issues.apache.org/jira/browse/PHOENIX-7249
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Anchal Kejriwal
>Assignee: Anchal Kejriwal
>Priority: Minor
> Labels: website
> Attachments: phoenix-website-1.patch, phoenix-website.patch
>
>
> [https://phoenix.apache.org/building_website.html]
> * cd site/publish
> * python -m SimpleHTTPServer 8000
> Running above with Python 3, gives error as {{{}No module named
> SimpleHTTPServer{}}}. It’s because in python 3, SimpleHTTPServer has been
> merged into {{http.server}} module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (PHOENIX-7252) Fix BackwardCompatibilityIT test failures
[ https://issues.apache.org/jira/browse/PHOENIX-7252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rushabh Shah updated PHOENIX-7252: -- Description: After PHOENIX-7166 once we set the default values of updateCacheFrequency to NEVER, there are many test failures in BackwardCompatibilityIT. See jenkins build here: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1778/46/#showFailuresLink was:After PHOENIX-7166 once we set the default values of updateCacheFrequency to NEVER, many > Fix BackwardCompatibilityIT test failures > - > > Key: PHOENIX-7252 > URL: https://issues.apache.org/jira/browse/PHOENIX-7252 > Project: Phoenix > Issue Type: Sub-task >Reporter: Rushabh Shah >Assignee: Rushabh Shah >Priority: Major > > After PHOENIX-7166 once we set the default values of updateCacheFrequency to > NEVER, there are many test failures in BackwardCompatibilityIT. > See jenkins build here: > https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1778/46/#showFailuresLink > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-7252) Fix BackwardCompatibilityIT test failures
[ https://issues.apache.org/jira/browse/PHOENIX-7252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rushabh Shah updated PHOENIX-7252: -- Description: After PHOENIX-7166 once we set the default values of updateCacheFrequency to NEVER, many > Fix BackwardCompatibilityIT test failures > - > > Key: PHOENIX-7252 > URL: https://issues.apache.org/jira/browse/PHOENIX-7252 > Project: Phoenix > Issue Type: Sub-task >Reporter: Rushabh Shah >Assignee: Rushabh Shah >Priority: Major > > After PHOENIX-7166 once we set the default values of updateCacheFrequency to > NEVER, many -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (PHOENIX-7252) Fix BackwardCompatibilityIT test failures
Rushabh Shah created PHOENIX-7252: - Summary: Fix BackwardCompatibilityIT test failures Key: PHOENIX-7252 URL: https://issues.apache.org/jira/browse/PHOENIX-7252 Project: Phoenix Issue Type: Sub-task Reporter: Rushabh Shah Assignee: Rushabh Shah -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (PHOENIX-7251) Refactor server-side code to support multiple ServerMetadataCache for HA tests
Palash Chauhan created PHOENIX-7251: --- Summary: Refactor server-side code to support multiple ServerMetadataCache for HA tests Key: PHOENIX-7251 URL: https://issues.apache.org/jira/browse/PHOENIX-7251 Project: Phoenix Issue Type: Sub-task Reporter: Palash Chauhan Assignee: Palash Chauhan In the metadata caching re-design, `ServerMetadataCache` is required to be a singleton in the implementation. This affects tests for the HA use case because the coprocessors on the 2 clusters end up using the same `ServerMetadataCache`. All tests which execute queries with 1 of the clusters unavailable will fail. We can refactor the implementation in the following way to support HA test cases: 1. Create a `ServerMetadataCache` interface and use the current implementation as `ServerMetadataCacheImpl` for all other tests. This would be a singleton. 2. Implement `ServerMetadataCacheHAImpl` with a map of instances keyed on config. 3. Extend `PhoenixRegionServerEndpoint` and use `ServerMetadataCacheHAImpl`. 4. In HA tests, load this new endpoint on the region servers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OMID-283) Support for build on mac M1
[
https://issues.apache.org/jira/browse/OMID-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823319#comment-17823319
]
Nikita Pande edited comment on OMID-283 at 3/4/24 8:08 PM:
---
[~stoty] thanks for inputs. I have updated my PR as per the comment.
Also can you please add me as contributor for this project?
was (Author: JIRAUSER298527):
[~stoty] thanks for inputs. I have updated my PR as per the comment.
> Support for build on mac M1
> ---
>
> Key: OMID-283
> URL: https://issues.apache.org/jira/browse/OMID-283
> Project: Phoenix Omid
> Issue Type: Improvement
>Reporter: Nikita Pande
>Priority: Major
>
> * Current code throws following error in `mvn install` command on mac M1
> *
> {noformat}
> [ERROR] Failed to execute goal
> org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:compile
> (compile-protoc) on project omid-common: Configuration error: Invalid
> artifact specification format, expected:
> groupId:artifactId:version[:type[:classifier]], actual:
> com.google.protobuf:protoc:osx-aarch_64:2.5.0:exe:osx-aarch_64 -> [Help
> 1]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OMID-283) Support for build on mac M1
[
https://issues.apache.org/jira/browse/OMID-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823319#comment-17823319
]
Nikita Pande commented on OMID-283:
---
[~stoty] thanks for inputs. I have updated my PR as per the comment.
> Support for build on mac M1
> ---
>
> Key: OMID-283
> URL: https://issues.apache.org/jira/browse/OMID-283
> Project: Phoenix Omid
> Issue Type: Improvement
>Reporter: Nikita Pande
>Priority: Major
>
> * Current code throws following error in `mvn install` command on mac M1
> *
> {noformat}
> [ERROR] Failed to execute goal
> org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:compile
> (compile-protoc) on project omid-common: Configuration error: Invalid
> artifact specification format, expected:
> groupId:artifactId:version[:type[:classifier]], actual:
> com.google.protobuf:protoc:osx-aarch_64:2.5.0:exe:osx-aarch_64 -> [Help
> 1]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OMID-283) Support for build on mac M1
[
https://issues.apache.org/jira/browse/OMID-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823313#comment-17823313
]
ASF GitHub Bot commented on OMID-283:
-
nikita15p opened a new pull request, #159:
URL: https://github.com/apache/phoenix-omid/pull/159
mvn -Pmac-m1 install will build the code successfully in the MAC M1 OS
> Support for build on mac M1
> ---
>
> Key: OMID-283
> URL: https://issues.apache.org/jira/browse/OMID-283
> Project: Phoenix Omid
> Issue Type: Improvement
>Reporter: Nikita Pande
>Priority: Major
>
> * Current code throws following error in `mvn install` command on mac M1
> *
> {noformat}
> [ERROR] Failed to execute goal
> org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:compile
> (compile-protoc) on project omid-common: Configuration error: Invalid
> artifact specification format, expected:
> groupId:artifactId:version[:type[:classifier]], actual:
> com.google.protobuf:protoc:osx-aarch_64:2.5.0:exe:osx-aarch_64 -> [Help
> 1]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OMID-284) Use protobuf 3 in Omid
[ https://issues.apache.org/jira/browse/OMID-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823307#comment-17823307 ] Istvan Toth commented on OMID-284: -- WDYT [~rajeshbabu] [~nihaljain.cs] [~larsh] ? > Use protobuf 3 in Omid > -- > > Key: OMID-284 > URL: https://issues.apache.org/jira/browse/OMID-284 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.1.2 >Reporter: Istvan Toth >Priority: Critical > > Omid uses Protobuf 2.5.0. > It only uses protobuf for communicating with the TSO server, it does not > implement an HBase endpoint, so I see no reason not to use the latest version. > This could be done in 1.2, provided that the switch does not cause > compatibility issues (I expect none) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OMID-284) Use protobuf 3 in Omid
[ https://issues.apache.org/jira/browse/OMID-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated OMID-284: - Description: Omid uses Protobuf 2.5.0. It only uses protobuf for communicating with the TSO server, it does not implement an HBase endpoint, so I see no reason not to use the latest version. This could be done in 1.2, provided that the switch does not cause compatibility issues (I expect none) > Use protobuf 3 in Omid > -- > > Key: OMID-284 > URL: https://issues.apache.org/jira/browse/OMID-284 > Project: Phoenix Omid > Issue Type: Improvement >Affects Versions: 1.1.2 >Reporter: Istvan Toth >Priority: Critical > > Omid uses Protobuf 2.5.0. > It only uses protobuf for communicating with the TSO server, it does not > implement an HBase endpoint, so I see no reason not to use the latest version. > This could be done in 1.2, provided that the switch does not cause > compatibility issues (I expect none) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OMID-284) Use protobuf 3 in Omid
Istvan Toth created OMID-284: Summary: Use protobuf 3 in Omid Key: OMID-284 URL: https://issues.apache.org/jira/browse/OMID-284 Project: Phoenix Omid Issue Type: Improvement Affects Versions: 1.1.2 Reporter: Istvan Toth -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OMID-276) Use HBase-thidrparty protobuf in Omid
[ https://issues.apache.org/jira/browse/OMID-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823298#comment-17823298 ] Istvan Toth commented on OMID-276: -- Omid actually uses protobuf 2.5.0 for some reason. The protocol looks super simple, I think we can upgrade to protobuf 3 libraries without problems. > Use HBase-thidrparty protobuf in Omid > - > > Key: OMID-276 > URL: https://issues.apache.org/jira/browse/OMID-276 > Project: Phoenix Omid > Issue Type: Wish >Affects Versions: 1.1.1 >Reporter: Istvan Toth >Priority: Major > > As Omid only supports HBase anyway, there is no reason not to use the > protobuf from HBase-thirdparty. > This removes an extra dependency, and makes life easier in Phoenix, where we > do not have to juggle two different protobuf 3 libraries. > This does require some refactoring as we need relocate the protobuf generated > files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OMID-283) Support for build on mac M1
[
https://issues.apache.org/jira/browse/OMID-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823297#comment-17823297
]
Istvan Toth commented on OMID-283:
--
This is already solved in Phoenix, it should be easy to copy the solution to
Omid (IIRC it is to use built-inm emulation to run the x86_64 version on ARM
Mac)
> Support for build on mac M1
> ---
>
> Key: OMID-283
> URL: https://issues.apache.org/jira/browse/OMID-283
> Project: Phoenix Omid
> Issue Type: Improvement
>Reporter: Nikita Pande
>Priority: Major
>
> * Current code throws following error in `mvn install` command on mac M1
> *
> {noformat}
> [ERROR] Failed to execute goal
> org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:compile
> (compile-protoc) on project omid-common: Configuration error: Invalid
> artifact specification format, expected:
> groupId:artifactId:version[:type[:classifier]], actual:
> com.google.protobuf:protoc:osx-aarch_64:2.5.0:exe:osx-aarch_64 -> [Help
> 1]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (OMID-283) Support for build on mac M1
Nikita Pande created OMID-283:
-
Summary: Support for build on mac M1
Key: OMID-283
URL: https://issues.apache.org/jira/browse/OMID-283
Project: Phoenix Omid
Issue Type: Improvement
Reporter: Nikita Pande
* Current code throws following error in `mvn install` command on mac M1
*
{noformat}
[ERROR] Failed to execute goal
org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:compile (compile-protoc)
on project omid-common: Configuration error: Invalid artifact specification
format, expected: groupId:artifactId:version[:type[:classifier]], actual:
com.google.protobuf:protoc:osx-aarch_64:2.5.0:exe:osx-aarch_64 -> [Help
1]{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OMID-277) Omid 1.1.2 fails with Phoenix 5.2
[
https://issues.apache.org/jira/browse/OMID-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823260#comment-17823260
]
Rajeshbabu Chintaguntla commented on OMID-277:
--
[~stoty] Yes Istvan. Testing in local clusters. Once it's fine will start RC.
> Omid 1.1.2 fails with Phoenix 5.2
> -
>
> Key: OMID-277
> URL: https://issues.apache.org/jira/browse/OMID-277
> Project: Phoenix Omid
> Issue Type: Bug
>Affects Versions: 1.1.1, 1.1.2
>Reporter: Lars Hofhansl
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 1.1.2
>
>
> Try to create a transactional table with Phoenix 5.2 and Omid 1.1.2, and
> you'll find this in the RS log:
> {code:java}
> 2024-02-28T20:26:13,055 ERROR [RS_OPEN_REGION-regionserver/think:16020-2]
> coprocessor.CoprocessorHost: The coprocessor
> org.apache.phoenix.coprocessor.OmidTransactionalProcessor threw
> java.lang.NoClassDefFoundE
> rror: Could not initialize class
> org.apache.omid.committable.hbase.HBaseCommitTableConfig
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.omid.committable.hbase.HBaseCommitTableConfig
> at
> org.apache.omid.transaction.OmidSnapshotFilter.start(OmidSnapshotFilter.java:85)
> ~[phoenix-server-hbase-2.5-5.2.0.jar:5.2.0]
> at
> org.apache.phoenix.coprocessor.OmidTransactionalProcessor.start(OmidTransactionalProcessor.java:44)
> ~[phoenix-server-hbase-2.5-5.2.0.jar:5.2.0]
> at
> org.apache.hadoop.hbase.coprocessor.BaseEnvironment.startup(BaseEnvironment.java:69)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.checkAndLoadInstance(CoprocessorHost.java:285)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.load(CoprocessorHost.java:249)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.load(CoprocessorHost.java:200)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.loadTableCoprocessors(RegionCoprocessorHost.java:388)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.(RegionCoprocessorHost.java:278)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at org.apache.hadoop.hbase.regionserver.HRegion.(HRegion.java:859)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at org.apache.hadoop.hbase.regionserver.HRegion.(HRegion.java:734)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at
> jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
> ~[?:?]
> at java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)
> ~[?:?]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:486) ~[?:?]
> at org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:6971)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegionFromTableDir(HRegion.java:7184)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7161)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7120)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at
> org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7076)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at
> org.apache.hadoop.hbase.regionserver.handler.AssignRegionHandler.process(AssignRegionHandler.java:149)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
> ~[hbase-server-2.5.7.jar:2.5.7]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[?:?]
> at java.lang.Thread.run(Thread.java:1583) ~[?:?]
> Caused by: java.lang.ExceptionInInitializerError: Exception
> java.lang.NoClassDefFoundError:
> org/apache/phoenix/shaded/com/google/common/base/Charsets [in thread
> "RS_OPEN_REGION-regionserver/think:16020-2"]
> at
> org.apache.omid.committable.hbase.HBaseCommitTableConfig.(HBaseCommitTableConfig.java:36)
> ~[phoenix-server-hbase-2.5-5.2.0.jar:5.2.0]
> at org.apache.omid.transaction.OmidCompactor.start(OmidCompactor.java:92)
> ~[phoenix-server-hbase-2.5-5.2.0.jar:5.2.0]
> at
> org.apache.phoenix.coprocessor.OmidGCProcessor.start(OmidGCProcessor.java:43)
> ~[phoenix-server-hbase-2.5-5.2.0.jar:5.2.0]
> ... 21 more{code}
>
> As before I have no time to track this down as I do not work on Phoenix/HBase
> anymore, but at least I can file an issue. :)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (PHOENIX-7250) Fix HBase log level in tests
[ https://issues.apache.org/jira/browse/PHOENIX-7250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-7250: - Priority: Major (was: Critical) > Fix HBase log level in tests > > > Key: PHOENIX-7250 > URL: https://issues.apache.org/jira/browse/PHOENIX-7250 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.2.0, 5.3.0, 5.1.4 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Labels: test > > When switching to log4j2, I made a typo in the logging config, which results > in HBase log level being set to WARN, instead of DEBUG that it was previously. > This makes debugging some test failures hard to impossbile. > Fix this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-7249) Starting HTTP Server with Python3 For website validation fails with error No module named SimpleHTTPServer
[
https://issues.apache.org/jira/browse/PHOENIX-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anchal Kejriwal updated PHOENIX-7249:
-
Labels: website (was: )
> Starting HTTP Server with Python3 For website validation fails with error No
> module named SimpleHTTPServer
> ---
>
> Key: PHOENIX-7249
> URL: https://issues.apache.org/jira/browse/PHOENIX-7249
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Anchal Kejriwal
>Assignee: Anchal Kejriwal
>Priority: Minor
> Labels: website
> Attachments: phoenix-website.patch
>
>
> [https://phoenix.apache.org/building_website.html]
> * cd site/publish
> * python -m SimpleHTTPServer 8000
> Running above with Python 3, gives error as {{{}No module named
> SimpleHTTPServer{}}}. It’s because in python 3, SimpleHTTPServer has been
> merged into {{http.server}} module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (PHOENIX-7249) Starting HTTP Server with Python3 For website validation fails with error No module named SimpleHTTPServer
[
https://issues.apache.org/jira/browse/PHOENIX-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anchal Kejriwal updated PHOENIX-7249:
-
Attachment: phoenix-website.patch
> Starting HTTP Server with Python3 For website validation fails with error No
> module named SimpleHTTPServer
> ---
>
> Key: PHOENIX-7249
> URL: https://issues.apache.org/jira/browse/PHOENIX-7249
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Anchal Kejriwal
>Assignee: Anchal Kejriwal
>Priority: Minor
> Attachments: phoenix-website.patch
>
>
> [https://phoenix.apache.org/building_website.html]
> * cd site/publish
> * python -m SimpleHTTPServer 8000
> Running above with Python 3, gives error as {{{}No module named
> SimpleHTTPServer{}}}. It’s because in python 3, SimpleHTTPServer has been
> merged into {{http.server}} module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (PHOENIX-7249) Starting HTTP Server with Python3 For website validation fails with error No module named SimpleHTTPServer
[
https://issues.apache.org/jira/browse/PHOENIX-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anchal Kejriwal updated PHOENIX-7249:
-
Summary: Starting HTTP Server with Python3 For website validation fails
with error No module named SimpleHTTPServer (was: Starting HTTP Server with
Python3 fails with error No module named SimpleHTTPServer)
> Starting HTTP Server with Python3 For website validation fails with error No
> module named SimpleHTTPServer
> ---
>
> Key: PHOENIX-7249
> URL: https://issues.apache.org/jira/browse/PHOENIX-7249
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Anchal Kejriwal
>Assignee: Anchal Kejriwal
>Priority: Minor
>
> [https://phoenix.apache.org/building_website.html]
> * cd site/publish
> * python -m SimpleHTTPServer 8000
> Running above with Python 3, gives error as {{{}No module named
> SimpleHTTPServer{}}}. It’s because in python 3, SimpleHTTPServer has been
> merged into {{http.server}} module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (PHOENIX-7249) Starting HTTP Server with Python3 fails with error No module named SimpleHTTPServer
[
https://issues.apache.org/jira/browse/PHOENIX-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anchal Kejriwal updated PHOENIX-7249:
-
Summary: Starting HTTP Server with Python3 fails with error No module named
SimpleHTTPServer (was: Generate Phoenix Website fails with error No module
named SimpleHTTPServer)
> Starting HTTP Server with Python3 fails with error No module named
> SimpleHTTPServer
> ---
>
> Key: PHOENIX-7249
> URL: https://issues.apache.org/jira/browse/PHOENIX-7249
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Anchal Kejriwal
>Assignee: Anchal Kejriwal
>Priority: Minor
>
> [https://phoenix.apache.org/building_website.html]
> * cd site/publish
> * python -m SimpleHTTPServer 8000
> Running above with Python 3, gives error as {{{}No module named
> SimpleHTTPServer{}}}. It’s because in python 3, SimpleHTTPServer has been
> merged into {{http.server}} module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (PHOENIX-7248) Add logging excludes to hadoop-mapreduce-client-app and hadoop-mapreduce-client-jobclient
[ https://issues.apache.org/jira/browse/PHOENIX-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-7248: - Affects Version/s: 5.2.0 5.3.0 5.1.4 > Add logging excludes to hadoop-mapreduce-client-app and > hadoop-mapreduce-client-jobclient > - > > Key: PHOENIX-7248 > URL: https://issues.apache.org/jira/browse/PHOENIX-7248 > Project: Phoenix > Issue Type: Improvement > Components: test >Affects Versions: 5.2.0, 5.3.0, 5.1.4 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > > Unwanted logging libraries are coming from these. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-7250) Fix HBase log level in tests
[ https://issues.apache.org/jira/browse/PHOENIX-7250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-7250: - Description: When switching to log4j2, I made a typo in the logging config, which results in HBase log level being set to WARN, instead of DEBUG that it was previously. This makes debugging some test failures hard to impossbile. Fix this. was: When switching to log4j2, I made a typo in the logging config, which results in HBase log level being set to WARN, instead of DEBUG that it was previously. This makes debugging some test failures hard to impossbile.Ű Fix this. > Fix HBase log level in tests > > > Key: PHOENIX-7250 > URL: https://issues.apache.org/jira/browse/PHOENIX-7250 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.2.0, 5.3.0, 5.1.4 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Critical > Labels: test > > When switching to log4j2, I made a typo in the logging config, which results > in HBase log level being set to WARN, instead of DEBUG that it was previously. > This makes debugging some test failures hard to impossbile. > Fix this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-7249) Generate Phoenix Website fails with error No module named SimpleHTTPServer
[
https://issues.apache.org/jira/browse/PHOENIX-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-7249:
-
Priority: Minor (was: Trivial)
> Generate Phoenix Website fails with error No module named SimpleHTTPServer
> --
>
> Key: PHOENIX-7249
> URL: https://issues.apache.org/jira/browse/PHOENIX-7249
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Anchal Kejriwal
>Assignee: Anchal Kejriwal
>Priority: Minor
>
> [https://phoenix.apache.org/building_website.html]
> * cd site/publish
> * python -m SimpleHTTPServer 8000
> Running above with Python 3, gives error as {{{}No module named
> SimpleHTTPServer{}}}. It’s because in python 3, SimpleHTTPServer has been
> merged into {{http.server}} module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (PHOENIX-7250) Fix HBase log level in tests
[ https://issues.apache.org/jira/browse/PHOENIX-7250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-7250: - Affects Version/s: 5.2.0 5.3.0 5.1.4 > Fix HBase log level in tests > > > Key: PHOENIX-7250 > URL: https://issues.apache.org/jira/browse/PHOENIX-7250 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.2.0, 5.3.0, 5.1.4 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Critical > Labels: test > > When switching to log4j2, I made a typo in the logging config, which results > in HBase log level being set to WARN, instead of DEBUG that it was previously. > This makes debugging some test failures hard to impossbile.Ű > Fix this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-7249) Generate Phoenix Website fails with error No module named SimpleHTTPServer
[
https://issues.apache.org/jira/browse/PHOENIX-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-7249:
-
Priority: Trivial (was: Major)
> Generate Phoenix Website fails with error No module named SimpleHTTPServer
> --
>
> Key: PHOENIX-7249
> URL: https://issues.apache.org/jira/browse/PHOENIX-7249
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Anchal Kejriwal
>Assignee: Anchal Kejriwal
>Priority: Trivial
>
> [https://phoenix.apache.org/building_website.html]
> * cd site/publish
> * python -m SimpleHTTPServer 8000
> Running above with Python 3, gives error as {{{}No module named
> SimpleHTTPServer{}}}. It’s because in python 3, SimpleHTTPServer has been
> merged into {{http.server}} module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (PHOENIX-7250) Fix HBase log level in tests
Istvan Toth created PHOENIX-7250: Summary: Fix HBase log level in tests Key: PHOENIX-7250 URL: https://issues.apache.org/jira/browse/PHOENIX-7250 Project: Phoenix Issue Type: Bug Components: core Reporter: Istvan Toth Assignee: Istvan Toth When switching to log4j2, I made a typo in the logging config, which results in HBase log level being set to WARN, instead of DEBUG that it was previously. This makes debugging some test failures hard to impossbile.Ű Fix this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-7250) Fix HBase log level in tests
[ https://issues.apache.org/jira/browse/PHOENIX-7250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-7250: - Labels: test (was: ) > Fix HBase log level in tests > > > Key: PHOENIX-7250 > URL: https://issues.apache.org/jira/browse/PHOENIX-7250 > Project: Phoenix > Issue Type: Bug > Components: core >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Critical > Labels: test > > When switching to log4j2, I made a typo in the logging config, which results > in HBase log level being set to WARN, instead of DEBUG that it was previously. > This makes debugging some test failures hard to impossbile.Ű > Fix this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (PHOENIX-7249) Generate Phoenix Website fails with error No module named SimpleHTTPServer
Anchal Kejriwal created PHOENIX-7249:
Summary: Generate Phoenix Website fails with error No module named
SimpleHTTPServer
Key: PHOENIX-7249
URL: https://issues.apache.org/jira/browse/PHOENIX-7249
Project: Phoenix
Issue Type: Improvement
Reporter: Anchal Kejriwal
[https://phoenix.apache.org/building_website.html]
* cd site/publish
* python -m SimpleHTTPServer 8000
Running above with Python 3, gives error as {{{}No module named
SimpleHTTPServer{}}}. It’s because in python 3, SimpleHTTPServer has been
merged into {{http.server}} module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (PHOENIX-7249) Generate Phoenix Website fails with error No module named SimpleHTTPServer
[
https://issues.apache.org/jira/browse/PHOENIX-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anchal Kejriwal reassigned PHOENIX-7249:
Assignee: Anchal Kejriwal
> Generate Phoenix Website fails with error No module named SimpleHTTPServer
> --
>
> Key: PHOENIX-7249
> URL: https://issues.apache.org/jira/browse/PHOENIX-7249
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Anchal Kejriwal
>Assignee: Anchal Kejriwal
>Priority: Major
>
> [https://phoenix.apache.org/building_website.html]
> * cd site/publish
> * python -m SimpleHTTPServer 8000
> Running above with Python 3, gives error as {{{}No module named
> SimpleHTTPServer{}}}. It’s because in python 3, SimpleHTTPServer has been
> merged into {{http.server}} module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (PHOENIX-7248) Add logging excludes to hadoop-mapreduce-client-app and hadoop-mapreduce-client-jobclient
[ https://issues.apache.org/jira/browse/PHOENIX-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-7248: - Description: Unwanted logging libraries are coming from these. (was: Unwanted logging libraries are coming from these (at least with Hadoop 3.3.5)) > Add logging excludes to hadoop-mapreduce-client-app and > hadoop-mapreduce-client-jobclient > - > > Key: PHOENIX-7248 > URL: https://issues.apache.org/jira/browse/PHOENIX-7248 > Project: Phoenix > Issue Type: Improvement > Components: test >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > > Unwanted logging libraries are coming from these. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (PHOENIX-7248) Add logging excludes to hadoop-mapreduce-client-app and hadoop-mapreduce-client-jobclient
Istvan Toth created PHOENIX-7248: Summary: Add logging excludes to hadoop-mapreduce-client-app and hadoop-mapreduce-client-jobclient Key: PHOENIX-7248 URL: https://issues.apache.org/jira/browse/PHOENIX-7248 Project: Phoenix Issue Type: Improvement Components: test Reporter: Istvan Toth Assignee: Istvan Toth Unwanted logging libraries are coming from these (at least with Hadoop 3.3.5) -- This message was sent by Atlassian Jira (v8.20.10#820010)
