Re: [Discuss] Phoenix Tech Talks
Hi All, The page for Phoenix Tech Talks has been added to the Apache Phoenix web site (see https://phoenix.apache.org/tech_talks.html) where all the information for upcoming and previous tech talks will be provided. The abstract for the talk at 9 AM PST on March 4 has been posted there. We are still working on finalizing the technical details of the video conferencing meeting, and I will update the meeting link on the page later. Thanks, Kadir On Wed, Feb 10, 2021 at 9:58 AM Kadir Ozdemir wrote: > I wanted to give an update on this. We are planning to have our first > Phoenix tech talk meeting on March 4th at 9am, and working on the details. > I will add a page on the Phoenix website for the tech talks and provide the > details there by the end of next week. Stay tuned! > > On Mon, Feb 8, 2021 at 2:00 PM Kadir Ozdemir > wrote: > >> Ankit, I was planning to include the user mailing list and it is good >> that you already did it. I like the idea of expanding talks to include >> use-cases. Thank you for the topic suggestions. >> >> >> On Mon, Feb 8, 2021 at 12:42 PM Ankit Singhal >> wrote: >> >>> This is excellent, thanks Kadir for initiating it, I am keen to listen to >>> your presentation on "strongly consistent global indexes". >>> Logistics looks great, however, if required can be adjusted as per the >>> feedback after the first meetup. >>> >>> Some of the current topics comes to my mind (in case someone wants to >>> share >>> their experiences with them) >>> * Improved python driver support ( Could be completely technical about >>> implementation or on the use-case >>> that how easy it is for any python developer to get started with >>> Phoenix/HBase) >>> * Key features in 4.16 and 5.1 release and upgrade path >>> * Adopted projects Apache Omid and Apache Tephra key differences. >>> >>> >>> +user to expand the scope of talks if someone >>> wants to present their use-cases. >>> >>> On Mon, Feb 8, 2021 at 9:06 AM Viraj Jasani wrote: >>> >>> > +1 to the idea of monthly meet-ups, and I will also do my best to join >>> in. >>> > Logistics part (when, durations etc) looks good to me. >>> > >>> > >>> > On Fri, 5 Feb 2021 at 1:36 AM, Josh Elser wrote: >>> > >>> > > Love it! I'll do my best to join in and listen (and participate later >>> > > on, too ;)) >>> > > >>> > > I joined one from Calcite a week or two ago. They did a signup via >>> > > Meetup.com and hosted it through Zoom. It felt very professional. >>> > > >>> > > On 2/4/21 12:10 PM, Kadir Ozdemir wrote: >>> > > > We are very excited to propose an idea that brings the Phoenix >>> > community >>> > > > together to have technical discussions on a recurring basis. The >>> goal >>> > is >>> > > to >>> > > > have a forum where we share technical knowledge we have acquired by >>> > > working >>> > > > on various aspects of Phoenix and to continue to bring innovation >>> and >>> > > > improvements as a community into Phoenix. We’d love to get >>> feedback on >>> > > this >>> > > > idea and determine the logistics for these meetings. >>> > > > >>> > > > Here is what we were thinking: >>> > > > >>> > > > - Come together as a community by hosting *Phoenix tech talks* >>> > once a >>> > > > month >>> > > > - The topics for these meetings can be any technical subject >>> > related >>> > > to >>> > > > Phoenix, including the architecture, internals, features and >>> > > interfaces of >>> > > > Phoenix, its operational aspects in the first party data >>> centers >>> > and >>> > > cloud, >>> > > > the technologies that it leverages (e.g., HBase and >>> Zookeeper), and >>> > > > technologies it can possibly leverage, adapt or follow >>> > > > >>> > > > *Logistics*: >>> > > > >>> > > > - *When*: First Thursday of each month at 9AM PST >>> > > > - *Duration*: 90 minutes (to allow the audience to participate >>> and >>> > > ask >>> > > > questions) >>> > > > - We will conduct these meetings over a video conference and >>> make >>> > the >>> > > > recordings available (we are sorting out the specifics) >>> > > > - The meeting agenda and past recordings will be available on >>> the >>> > > Apache >>> > > > Phoenix site >>> > > > >>> > > > We need a coordinator for these meetings to set the agenda and >>> manage >>> > its >>> > > > logistics. I will volunteer to organize these meetings and curate >>> the >>> > > > topics for the tech talks, at least initially. To get the ball >>> > rolling, I >>> > > > will present the strongly consistent global indexes in the first >>> > meeting. >>> > > > What do you think about this proposal? >>> > > > >>> > > > Thanks, >>> > > > Kadir >>> > > > >>> > > >>> > >>> >>
[jira] [Updated] (PHOENIX-6271) Effective DDL generated by SchemaExtractionTool should maintain the order of PK and other columns
[ https://issues.apache.org/jira/browse/PHOENIX-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam updated PHOENIX-6271: Fix Version/s: 4.16.1 5.1.1 > Effective DDL generated by SchemaExtractionTool should maintain the order of > PK and other columns > - > > Key: PHOENIX-6271 > URL: https://issues.apache.org/jira/browse/PHOENIX-6271 > Project: Phoenix > Issue Type: Improvement >Reporter: Swaroopa Kadam >Assignee: Swaroopa Kadam >Priority: Minor > Fix For: 5.1.1, 4.16.1 > > > SchemaExtractionTool is used to generate effective DDL which can be then > compared with the DDL on the cluster to perform schema monitoring. > This won't affect the monitoring part but would be good to have the PR order > in place so that effective DDL can be used for creating the entity for the > first time in a new environment. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6397) Implement TableMetricsManager class and its associated functions for select. upsert and Delete Queries
[ https://issues.apache.org/jira/browse/PHOENIX-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] vikas meka updated PHOENIX-6397: Fix Version/s: 5.2.0 4.17.0 > Implement TableMetricsManager class and its associated functions for select. > upsert and Delete Queries > -- > > Key: PHOENIX-6397 > URL: https://issues.apache.org/jira/browse/PHOENIX-6397 > Project: Phoenix > Issue Type: Sub-task >Reporter: vikas meka >Assignee: vikas meka >Priority: Major > Fix For: 4.17.0, 5.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6397) Implement TableMetricsManager class and its associated functions for select. upsert and Delete Queries
[ https://issues.apache.org/jira/browse/PHOENIX-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] vikas meka reassigned PHOENIX-6397: --- Assignee: vikas meka > Implement TableMetricsManager class and its associated functions for select. > upsert and Delete Queries > -- > > Key: PHOENIX-6397 > URL: https://issues.apache.org/jira/browse/PHOENIX-6397 > Project: Phoenix > Issue Type: Sub-task >Reporter: vikas meka >Assignee: vikas meka >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6397) Implement TableMetricsManager class and its associated functions for select. upsert and Delete Queries
vikas meka created PHOENIX-6397: --- Summary: Implement TableMetricsManager class and its associated functions for select. upsert and Delete Queries Key: PHOENIX-6397 URL: https://issues.apache.org/jira/browse/PHOENIX-6397 Project: Phoenix Issue Type: Sub-task Reporter: vikas meka -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (PHOENIX-6391) Please tidy up Incubator releases
[ https://issues.apache.org/jira/browse/PHOENIX-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb closed PHOENIX-6391. - Thanks! > Please tidy up Incubator releases > - > > Key: PHOENIX-6391 > URL: https://issues.apache.org/jira/browse/PHOENIX-6391 > Project: Phoenix > Issue Type: Bug >Reporter: Sebb >Assignee: Ankit Singhal >Priority: Major > > The following directory trees appear to be obsolete, and should be deleted > please: > https://dist.apache.org/repos/dist/release/incubator/omid/ > https://dist.apache.org/repos/dist/dev/incubator/omid/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (PHOENIX-6393) Please tidy up Incubator releases
[ https://issues.apache.org/jira/browse/PHOENIX-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb closed PHOENIX-6393. - Thanks! > Please tidy up Incubator releases > - > > Key: PHOENIX-6393 > URL: https://issues.apache.org/jira/browse/PHOENIX-6393 > Project: Phoenix > Issue Type: Bug >Reporter: Sebb >Assignee: Ankit Singhal >Priority: Major > > The following directory trees appear to be obsolete, and should be removed > please: > https://dist.apache.org/repos/dist/release/incubator/tephra/ > https://dist.apache.org/repos/dist/dev/incubator/tephra/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OMID-200) Omid client cannot use kerberos cache when using proxyUser
[ https://issues.apache.org/jira/browse/OMID-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved OMID-200. -- Fix Version/s: 1.0.3 Resolution: Fixed Committed to master. Thanks for the review [~rajeshbabu] > Omid client cannot use kerberos cache when using proxyUser > -- > > Key: OMID-200 > URL: https://issues.apache.org/jira/browse/OMID-200 > Project: Phoenix Omid > Issue Type: Bug >Affects Versions: 1.0.2 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Blocker > Fix For: 1.0.3 > > > The HBase login code with the OMID-199 patch now works for the "normal" case, > however, it fails when proxyusers are involved. > Effectively, secure connections via Phoenix Query Servers are still not > working with Omid. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [phoenix-omid] stoty closed pull request #91: OMID-200 Omid client cannot use kerberos cache when using proxyUser
stoty closed pull request #91: URL: https://github.com/apache/phoenix-omid/pull/91 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 a change in pull request #89: OMID-198 Replace static ports used for TSO server with random ports i…
stoty commented on a change in pull request #89:
URL: https://github.com/apache/phoenix-omid/pull/89#discussion_r582668337
##
File path:
tso-server/src/test/java/org/apache/omid/tso/TestTSOChannelHandlerNetty.java
##
@@ -70,186 +72,197 @@
private
RequestProcessor requestProcessor;
-// Component under test
-private TSOChannelHandler channelHandler;
-
@BeforeMethod
public void beforeTestMethod() {
MockitoAnnotations.initMocks(this);
-TSOServerConfig config = new TSOServerConfig();
-config.setPort(1434);
-channelHandler = new TSOChannelHandler(config, requestProcessor, new
NullMetricsProvider());
}
-@AfterMethod
-public void afterTestMethod() throws IOException {
-channelHandler.close();
+private TSOChannelHandler getTSOChannelHandler(int port) {
+TSOServerConfig config = new TSOServerConfig();
+config.setPort(port);
+return new TSOChannelHandler(config, requestProcessor, new
NullMetricsProvider());
}
@Test(timeOut = 10_000)
public void testMainAPI() throws Exception {
-
-// Check initial state
-assertNull(channelHandler.listeningChannel);
-assertNull(channelHandler.channelGroup);
-
-// Check initial connection
-channelHandler.reconnect();
-assertTrue(channelHandler.listeningChannel.isOpen());
-assertEquals(channelHandler.channelGroup.size(), 1);
-assertEquals(((InetSocketAddress)
channelHandler.listeningChannel.getLocalAddress()).getPort(), 1434);
-
-// Check connection close
-channelHandler.closeConnection();
-assertFalse(channelHandler.listeningChannel.isOpen());
-assertEquals(channelHandler.channelGroup.size(), 0);
-
-// Check re-closing connection
-channelHandler.closeConnection();
-assertFalse(channelHandler.listeningChannel.isOpen());
-assertEquals(channelHandler.channelGroup.size(), 0);
-
-// Check connection after closing
-channelHandler.reconnect();
-assertTrue(channelHandler.listeningChannel.isOpen());
-assertEquals(channelHandler.channelGroup.size(), 1);
-
-// Check re-connection
-channelHandler.reconnect();
-assertTrue(channelHandler.listeningChannel.isOpen());
-assertEquals(channelHandler.channelGroup.size(), 1);
-
-// Exercise closeable with re-connection trial
-channelHandler.close();
-assertFalse(channelHandler.listeningChannel.isOpen());
-assertEquals(channelHandler.channelGroup.size(), 0);
+int port = NetworkUtils.getFreePort();
+TSOChannelHandler channelHandler = getTSOChannelHandler(port);
try {
+// Check initial state
+assertNull(channelHandler.listeningChannel);
+assertNull(channelHandler.channelGroup);
+
+// Check initial connection
channelHandler.reconnect();
-} catch (ChannelException e) {
-// Expected: Can't reconnect after closing
+assertTrue(channelHandler.listeningChannel.isOpen());
+assertEquals(channelHandler.channelGroup.size(), 1);
+assertEquals(((InetSocketAddress)
channelHandler.listeningChannel.getLocalAddress()).getPort(), port);
+
+// Check connection close
+channelHandler.closeConnection();
assertFalse(channelHandler.listeningChannel.isOpen());
assertEquals(channelHandler.channelGroup.size(), 0);
-}
+// Check re-closing connection
+channelHandler.closeConnection();
+assertFalse(channelHandler.listeningChannel.isOpen());
+assertEquals(channelHandler.channelGroup.size(), 0);
+
+// Check connection after closing
+channelHandler.reconnect();
+assertTrue(channelHandler.listeningChannel.isOpen());
+assertEquals(channelHandler.channelGroup.size(), 1);
+
+// Check re-connection
+channelHandler.reconnect();
+assertTrue(channelHandler.listeningChannel.isOpen());
+assertEquals(channelHandler.channelGroup.size(), 1);
+
+// Exercise closeable with re-connection trial
+channelHandler.close();
+assertFalse(channelHandler.listeningChannel.isOpen());
+assertEquals(channelHandler.channelGroup.size(), 0);
+try {
+channelHandler.reconnect();
Review comment:
If this is not supposed to succed, then please add an Assert.fail after.
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 a change in pull request #89: OMID-198 Replace static ports used for TSO server with random ports i…
stoty commented on a change in pull request #89:
URL: https://github.com/apache/phoenix-omid/pull/89#discussion_r582666495
##
File path:
hbase-client/src/test/java/org/apache/omid/transaction/OmidTestBase.java
##
@@ -99,12 +102,12 @@ public void beforeGroups(ITestContext context) throws
Exception {
HBaseTimestampStorageConfig hBaseTimestampStorageConfig =
injector.getInstance(HBaseTimestampStorageConfig.class);
tso.startAsync();
tso.awaitRunning();
-TestUtils.waitForSocketListening("localhost", 1234, 100);
+TestUtils.waitForSocketListening("localhost", port, 100);
LOG.info("Finished loading TSO");
context.setAttribute("tso", tso);
OmidClientConfiguration clientConf = new OmidClientConfiguration();
-clientConf.setConnectionString("localhost:1234");
+clientConf.setConnectionString("localhost:"+port);
Review comment:
please add spaces around "+" here, and every such occurence
##
File path:
hbase-client/src/test/java/org/apache/omid/transaction/TestFilters.java
##
@@ -71,9 +71,8 @@ public void testGetWithValueFilter(ITestContext context)
throws Exception {
private void testGet(ITestContext context, Filter f) throws Exception {
CommitTable.Client commitTableClient =
spy(getCommitTable(context).getClient());
-
HBaseOmidClientConfiguration hbaseOmidClientConf = new
HBaseOmidClientConfiguration();
-hbaseOmidClientConf.setConnectionString("localhost:1234");
+hbaseOmidClientConf.setConnectionString("localhost:"+port+"");
Review comment:
The last +"" is not needed, please remove it everywhere in the patch.
##
File path:
tso-server/src/test/java/org/apache/omid/tso/TestTSOChannelHandlerNetty.java
##
@@ -70,186 +72,197 @@
private
RequestProcessor requestProcessor;
-// Component under test
-private TSOChannelHandler channelHandler;
-
@BeforeMethod
public void beforeTestMethod() {
MockitoAnnotations.initMocks(this);
-TSOServerConfig config = new TSOServerConfig();
-config.setPort(1434);
-channelHandler = new TSOChannelHandler(config, requestProcessor, new
NullMetricsProvider());
}
-@AfterMethod
-public void afterTestMethod() throws IOException {
-channelHandler.close();
+private TSOChannelHandler getTSOChannelHandler(int port) {
+TSOServerConfig config = new TSOServerConfig();
+config.setPort(port);
+return new TSOChannelHandler(config, requestProcessor, new
NullMetricsProvider());
}
@Test(timeOut = 10_000)
public void testMainAPI() throws Exception {
-
-// Check initial state
-assertNull(channelHandler.listeningChannel);
-assertNull(channelHandler.channelGroup);
-
-// Check initial connection
-channelHandler.reconnect();
-assertTrue(channelHandler.listeningChannel.isOpen());
-assertEquals(channelHandler.channelGroup.size(), 1);
-assertEquals(((InetSocketAddress)
channelHandler.listeningChannel.getLocalAddress()).getPort(), 1434);
-
-// Check connection close
-channelHandler.closeConnection();
-assertFalse(channelHandler.listeningChannel.isOpen());
-assertEquals(channelHandler.channelGroup.size(), 0);
-
-// Check re-closing connection
-channelHandler.closeConnection();
-assertFalse(channelHandler.listeningChannel.isOpen());
-assertEquals(channelHandler.channelGroup.size(), 0);
-
-// Check connection after closing
-channelHandler.reconnect();
-assertTrue(channelHandler.listeningChannel.isOpen());
-assertEquals(channelHandler.channelGroup.size(), 1);
-
-// Check re-connection
-channelHandler.reconnect();
-assertTrue(channelHandler.listeningChannel.isOpen());
-assertEquals(channelHandler.channelGroup.size(), 1);
-
-// Exercise closeable with re-connection trial
-channelHandler.close();
-assertFalse(channelHandler.listeningChannel.isOpen());
-assertEquals(channelHandler.channelGroup.size(), 0);
+int port = NetworkUtils.getFreePort();
+TSOChannelHandler channelHandler = getTSOChannelHandler(port);
try {
+// Check initial state
+assertNull(channelHandler.listeningChannel);
+assertNull(channelHandler.channelGroup);
+
+// Check initial connection
channelHandler.reconnect();
-} catch (ChannelException e) {
-// Expected: Can't reconnect after closing
+assertTrue(channelHandler.listeningChannel.isOpen());
+assertEquals(channelHandler.channelGroup.size(), 1);
+assertEquals(((InetSocketAddress)
channelHandler.listeningChannel.getLocalAddress()).getPort(), port);
+
+// Check connection close
+
[GitHub] [phoenix-omid] stoty opened a new pull request #91: OMID-200 Omid client cannot use kerberos cache when using proxyUser
stoty opened a new pull request #91: URL: https://github.com/apache/phoenix-omid/pull/91 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
