Re: Apache HAWQ 2.3.0.0 release plan

Umbrella JIRAS on that page as well. > > Best, > Yi Jin (yjin) > > On Thu, Jul 20, 2017 at 3:52 PM, Vineet Goel <vvin...@apache.org> wrote: > > > Hi Yi, > > > > Thank you for the initiative. I have some feedback that we can discuss > here > > and co

Re: Apache HAWQ 2.3.0.0 release plan

Hi Yi, Thank you for the initiative. I have some feedback that we can discuss here and collect further input on. a) Putting a timeline on releases (such as October 31st here) may have some downsides to the process. My thoughts are that more frequent releases give users access to features and

Re: Layout of LICENSE, NOTICE, and DISCLAIMER files for Apache HAWQ 2.2.0.0-incubating rpm binary release

Ed, +1 to that idea. Ranger component is technically optional and I think we should release without it and resolve that in the next version. This will keep the momentum going ... Thanks On Tue, Jun 6, 2017 at 12:22 AM Ed Espino wrote: > Roman, > > If we cannot resolve the

[jira] [Created] (HAWQ-1472) Support 'alter role set' statements in HAWQ

Vineet Goel created HAWQ-1472: - Summary: Support 'alter role set' statements in HAWQ Key: HAWQ-1472 URL: https://issues.apache.org/jira/browse/HAWQ-1472 Project: Apache HAWQ Issue Type: New

[jira] [Created] (HAWQ-1467) PXF HiveVectorizedORC profile should support Predicate Pushdown

Vineet Goel created HAWQ-1467: - Summary: PXF HiveVectorizedORC profile should support Predicate Pushdown Key: HAWQ-1467 URL: https://issues.apache.org/jira/browse/HAWQ-1467 Project: Apache HAWQ

[jira] [Created] (HAWQ-1466) PXF HiveVectorizedORC profile should handle complex types

Vineet Goel created HAWQ-1466: - Summary: PXF HiveVectorizedORC profile should handle complex types Key: HAWQ-1466 URL: https://issues.apache.org/jira/browse/HAWQ-1466 Project: Apache HAWQ Issue

Re: ALTER ROLE SET Statements

ers > Lei > > > > On Thu, May 11, 2017 at 11:11 AM, Vineet Goel <vvin...@apache.org> wrote: > > > Hi all, > > > > Does anyone have some historical context on why 'alter role set' > statements > > are not supported ? > > > > htt

ALTER ROLE SET Statements

Hi all, Does anyone have some historical context on why 'alter role set' statements are not supported ? https://github.com/apache/incubator-hawq/blob/master/src/backend/tcop/utility.c#L1654 gpadmin=# alter role gpadmin SET search_path TO myschema; ERROR: Cannot support alter role set statement

[jira] [Created] (HAWQ-1442) Upgrade Parquet format version in HAWQ

Vineet Goel created HAWQ-1442: - Summary: Upgrade Parquet format version in HAWQ Key: HAWQ-1442 URL: https://issues.apache.org/jira/browse/HAWQ-1442 Project: Apache HAWQ Issue Type: New Feature

Re: Design of HAWQ RPS HA

Thank you for posting this design doc. There is a great design discussion that has started on the JIRA as a result. We could create new JIRAs for some of the suggestions and take an iterative approach to developing this. -Vineet On Tue, Apr 25, 2017 at 6:44 PM Ma Hongxu

Re: PXF JDBC plugin

Devin and others, It would be great if you can expand a bit more on the implementation or point to a document? Thanks! On Mon, Apr 3, 2017 at 7:53 AM Jon Roberts wrote: > JDBC PXF is pretty exciting. Are there details on how this works? > > Does PXF randomly pick a

Re: DRAFT: ASF HAWQ Incubator PMC report for April 2017

Looks great ! On Fri, Mar 31, 2017 at 9:17 PM Ed Espino wrote: > Ruilong, > > Thanks buddy. January 123!!! :) a typo indeed. I have updated the report. > > -=e > > On Fri, Mar 31, 2017 at 7:18 PM, Ruilong Huo wrote: > > > Hi Ed, > > > > One typo is that

[jira] [Created] (HAWQ-1416) hawq_toolkit administrative schema missing in HAWQ installation

Vineet Goel created HAWQ-1416: - Summary: hawq_toolkit administrative schema missing in HAWQ installation Key: HAWQ-1416 URL: https://issues.apache.org/jira/browse/HAWQ-1416 Project: Apache HAWQ

Re: hawq Ambari integration

/REVOKE is > > executed in HAWQ it will be replicated to Ranger and when a GRANT/REVOKE > is > > executed in Ranger, it will be replicated to HAWQ. Right? If yes, then > > this is the model that I'm suggesting for Ambari. > > > > Jon Roberts > > Principal Engineer | j

Re: hawq Ambari integration

Having worked with Ambari and knowing the complexities of this desired integration, I agree with Alex on his comments below. Users need some time to get used to exclusive HAWQ CLI or Ambari usage model, and avoid mix and match despite the fact that HAWQ CLI and Ambari have their

Re: Apache HAWQ & Pivotal HDB release alignment

diversity of participants in the Hadoop > project. But we have not found this confusing for our customers. > > Alan. > > > On Feb 16, 2017, at 8:39 PM, Vineet Goel <vvin...@apache.org> wrote: > > > > Hi everyone, > > > > Let me try to clarify the request if

Re: Apache HAWQ & Pivotal HDB release alignment

> > +1 for consistence > > > > > > > > > > > > On Thu, Feb 16, 2017 at 10:40 AM, Ed Espino < > esp...@apache.org > > > > > > > wrote: > > > > > > > > > >

Re: HAWQ Upgarde Issues

Gagan - thank you for reporting this. To be specific - how exactly did you update pg_proc catalog table? On Sun, Feb 5, 2017 at 8:59 AM Gagan Brahmi wrote: > So finally I was able to figure out the problem. > > The system catalog table for pg_proc needed to be updated.

Re: [DISCUSS] Switch HAWQ to Java 8

HAWQ PXF already supports Java 8. There were some Javadocs warnings that Alex fixed recently: https://issues.apache.org/jira/browse/HAWQ-1308 I believe we will need to do PL/Java changes at some point: https://issues.apache.org/jira/browse/HAWQ-935 (PL/java support for jdk 1.8) Are there other

Re: Secure PXF HCatalog Issues

Hi Gagan, Check the recent Pull Request by Kavinder, which should solve this issue: https://github.com/apache/incubator-hawq/pull/1075 Hi Kavinder - should JIRA HAWQ-762 be set to resolved? The fix will get included in the next (or next+1) Apache HAWQ release as well as the next HDB release.

Re: DISCUSSION NEEDED: 2.1.0.0-incubating - what to do with unresolved JIRAs

Agree with Ruilong. And for JIRA owners, please remember to update the Fix Version when you close a JIRA. There are many JIRAs which are resolved/closed but Fix Version = Backlog, which is very confusing for a someone looking to see which release has the fix. On Thu, Dec 22, 2016 at 4:52 PM

Re: New Committer: Hong Wu

Congrats ! On Thu, Nov 3, 2016 at 11:39 PM 陶征霖 wrote: > Congratulations! > > 2016-11-04 14:24 GMT+08:00 Radar Da lei : > > > Congratulations Hong! > > > > Regards, > > Radar > > > > On Fri, Nov 4, 2016 at 2:16 PM, Ruilong Huo wrote: > > >

[jira] [Created] (HAWQ-1111) Support for IN() operation in PXF

Vineet Goel created HAWQ-: - Summary: Support for IN() operation in PXF Key: HAWQ- URL: https://issues.apache.org/jira/browse/HAWQ- Project: Apache HAWQ Issue Type: New Feature

Re: [ANNOUNCE] Apache HAWQ 2.0.0.0-incubating Released

Proud of the HAWQ community members coming together to make this happen ! It's a major milestone. Congrats, Vineet On Mon, Oct 10, 2016 at 1:01 PM Goden Yao wrote: > Hi, > > > > Apache HAWQ(incubating) Project Team is proud to announce that the very 1st > > deliverable:

Re: Would you like to Tweet for @ApacheHAWQ?

Count me in, I'd be happy to participate and assist. Thanks Vineet *@vVineet* On Mon, Oct 10, 2016 at 12:59 PM Greg Chase wrote: > Greetings HAWQ community, > > It seems the prior crew of people who volunteered to Tweet for @ApacheHAWQ > > are less active in the community

Re: Podling Report Reminder - October 2016

Hi Lei, Thanks for drafting the report. It will be good to include the following points as well: a) Two meetups on HAWQ conducted on Sept 21 and 22: Data Science at Scale with HAWQ and MADlib and Hadoop https://www.meetup.com/Data-Engineers-Guild/events/233974633/

Re: [VOTE] Apache HAWQ 2.0.0.0-incubating RC3

Seems like the pending issues are resolved, so we're good to go with RC4 now. Ed - would u agree? On Thu, Sep 22, 2016 at 10:23 AM Goden Yao wrote: > I want to check if the community thinks we're ready to spin up another RC4 > voting. > Let me know so I can prepare the

Re: Re: External scan error: There are more external files (URLs) than primary segments that can read them (COptTasks.cpp:1756)

gment_directory Value : > GUC : seq_page_cost Value : 1 > GUC : server_encoding Value : UTF8 > GUC : server_ticket_renew_interval Value : 4320 > GUC : server_version Value : 8.2.15 > GUC : server_version_num Value : 80215 > GUC : shared_buffers Value : 4000 > GUC : shared_preload_librarie

Co-located Joins & Data Locality in HAWQ

Hi all, I have received a fair number of questions on the topic of handling data locality and co-located joins in HAWQ 2. Most of the questions are coming from the background where HAWQ 1.x defaulted to HASH distributed tables distributed by a key and hence resulted in local joins in most cases

Re: External scan error: There are more external files (URLs) than primary segments that can read them (COptTasks.cpp:1756)

Could you please post your SQL DDL statement? How many URLs do you have in your external table? Also, your HASH dist table - how many buckets are defined, if any? Are the # of URLs more than the # of buckets or default_hash_table_bucket_number value? Perhaps you can attach your hawq-site.xml file

Re: New Committer: Kavinder Dhaliwal (Announcement)

Congrats on becoming an Apache HAWQ committer ! On Tue, Sep 13, 2016 at 11:48 AM Oleksandr Diachenko wrote: > Congratulations Kavinder, well deserved! > > On Tue, Sep 13, 2016 at 11:13 AM, Shivram Mani > wrote: > > > Congrats Kavinder. Your

HAWQ and Azure blob storage

Recently, a question came up whether HAWQ can support Azure with it's blob storage (WASB), given that WASB is HDFS compatible. I wanted to get the developer community's thoughts on HAWQ compatibility. It seems to me that HAWQ will not work as-is with WASB, right? Some investigation and

Re: A question of HAWQ (update/delete)

Update and Delete is not supported yet, but it's in the future plan. There is a JIRA on it I believe: https://issues.apache.org/jira/browse/HAWQ-304 Out of curiosity, what specific scenario are you trying to solve that requires update/delete ? -Vineet On Tue, Jul 12, 2016 at 7:10 PM, jinzhy

Re: Question on hawq_rm_nvseg_perquery_limit

on, it is not necessary to adjust > hawq_rm_nvseg_perquery_limit, > > say, we just need to leave it unchanged and actually not active until we > > really want to run a large-scale HAWQ cluster, for example, 100+ nodes. > > > > Best, > >

Question on hawq_rm_nvseg_perquery_limit

Hi all, I’m trying to document some GUC usage in detail and have questions on hawq_rm_nvseg_perquery_limit and hawq_rm_nvseg_perquery_perseg_limit tuning. *hawq_rm_nvseg_perquery_limit* = (default value = 512) . Let’s call it *perquery_limit* in short. *hawq_rm_nvseg_perquery_perseg_limit*

question on pg_hba.conf updates

Hi all, Question related to integration with Apache Ambari. It would be nice to make pg_hba.conf visible and editable in Ambari, so that Ambari allows one single interface for admins to update HAWQ and System configs such as hawq-site.xml, hawq-check.conf, sysctl.conf, limits.conf,

Re: [VOTE] HAWQ 2.0.0-incubating Release

status. > > Re-create the branch can make all our good changes in, and it's more clear, > users can easy find out where it cut out, just following one version change > commit. > > Anyway, I'm fine with each way. Thanks. > > Regards, > Radar > > On Thu, Jul 7, 2016 at

Re: [VOTE] HAWQ 2.0.0-incubating Release

Radar, The whole point of cutting a branch was to stabilize it for the first release. Why would we discard it and start a new one from master? Any changes since the 2.0.0-incubating branch needs to go in the next release scope (unless selective back-porting is necessary to meet the first release

Re: Confusion around HAWQ versions in JIRA

t described above, I think 4 > digit > > > > make > > > > > more sense. And from it, user can easily know whether specific > > upgrade > > > > > process needed or just binary switch if fine. > > > > > Based on that, for the "2.

Re: Confusion around HAWQ versions in JIRA

1) Proposal - we can rename the 2.0.0 version to 2.0.1-incubating as the next planned maintenance release (for now). All JIRAs targeted for 2.0.0 should be evaluated to see if any belong to the scope for the upcoming 2.0.0-incubating release or not. 2) Regarding comments on JIRA-875, I have

[jira] [Created] (HAWQ-895) Investigate migration to 3-digit Semantic versioning

Vineet Goel created HAWQ-895: Summary: Investigate migration to 3-digit Semantic versioning Key: HAWQ-895 URL: https://issues.apache.org/jira/browse/HAWQ-895 Project: Apache HAWQ Issue Type

Re: elastic execution engine question

What about hawq_rm_stmt_nvseg ? http://hdb.docs.pivotal.io/20/reference/guc/parameter_definitions.html#hawq_rm_stmt_nvseg -Vineet On Jun 30, 2016, at 6:43 PM, Hubert Zhang wrote: You can try to the GUC enforce_virtual_segment_number. It works for queries without UDF.

Re: Podling Report Reminder - July 2016

looks good to me. Thanks -Vineet On Wed, Jun 29, 2016 at 2:49 AM, Lei Chang wrote: > Hi Guys, > > Please see the following report. Looking forwards to your comments & > suggestions! > > --- > Apache HAWQ is a

Re: [Propose] Create a new HAWQ roadmap page

+1 too I can help start a draft on the wiki based on historical user requests and trends in the ecosystem. And of course, the roadmap is a living and breathing document which will continue to evolve over time based on continuous feedback, and more. -Vineet On Thu, Jun 23, 2016 at 8:18 AM,

Re: First HAWQ release

+1 to the proposed release name and cutting a release branch asap. Sounds like we need to find a good commit point right after the Apache release requirements were met (quicklz removal etc). -Vineet On Mon, Jun 20, 2016 at 2:13 PM, Ting(Goden) Yao wrote: > I can start the

Re: Master Segment Communication Issues

Are you using vagrant or VMs, or are these physical machines? Sometimes, the problem can result from the misleading IP address configuration of network card in virtual machine. Check if two segments have the same IP address in eth0. You must specify different IP address of eth0 of different