Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B1E8C200C0A for ; Sat, 14 Jan 2017 05:57:53 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id B0740160B47; Sat, 14 Jan 2017 04:57:53 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 063B6160B3F for ; Sat, 14 Jan 2017 05:57:52 +0100 (CET) Received: (qmail 57839 invoked by uid 500); 14 Jan 2017 04:57:52 -0000 Mailing-List: contact dev-help@apex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.apache.org Delivered-To: mailing list dev@apex.apache.org Received: (qmail 57828 invoked by uid 99); 14 Jan 2017 04:57:52 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Jan 2017 04:57:52 +0000 Received: from mail-ot0-f175.google.com (mail-ot0-f175.google.com [74.125.82.175]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id D8C511A0329 for ; Sat, 14 Jan 2017 04:57:51 +0000 (UTC) Received: by mail-ot0-f175.google.com with SMTP id 73so14421535otj.0 for ; Fri, 13 Jan 2017 20:57:51 -0800 (PST) X-Gm-Message-State: AIkVDXLonOMa68D2UOehztXsQZU3Cjtm3KgdVJeVHw3vO7f1ruY1Es/QTknTLBiG5g4w2cNxLfDRhUeioB11Gw== X-Received: by 10.157.13.166 with SMTP id 35mr12113287ots.140.1484369871148; Fri, 13 Jan 2017 20:57:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.24.38 with HTTP; Fri, 13 Jan 2017 20:57:50 -0800 (PST) In-Reply-To: References: From: Yogi Devendra Date: Sat, 14 Jan 2017 10:27:50 +0530 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: APEXMALHAR-2382 User needs to create dt_meta table while using JdbcPOJOInsertOutputOperator To: dev Content-Type: multipart/alternative; boundary=94eb2c033158e2a2d7054606cae0 archived-at: Sat, 14 Jan 2017 04:57:53 -0000 --94eb2c033158e2a2d7054606cae0 Content-Type: text/plain; charset=UTF-8 As Aniruddha pointed out, table creation should be done by dbadmin. In that case, utility script will be helpful. If we embed this code inside operator or application; then it will be difficult for dbadmin to use it. ~ Yogi On 14 January 2017 at 03:43, Thomas Weise wrote: > -1 for automatic schema modification, unless the user asked for it. See > comment on JIRA. > > > On Fri, Jan 13, 2017 at 5:11 AM, Aniruddha Thombare < > aniruddha@datatorrent.com> wrote: > > > The tables should be created / altered by dbadmin. > > We shouldn't worry about table creations as its one-time activity. > > > > > > > > Thanks, > > > > A > > > > > > _____________________________________ > > Sent with difficulty, I mean handheld ;) > > > > On 13 Jan 2017 6:37 pm, "Yogi Devendra" wrote: > > > > I am not very keen on having utility script. > > But, "no side-effects without explicit ask by the end-user" is important. > > > > ~ Yogi > > > > On 13 January 2017 at 16:44, Priyanka Gugale wrote: > > > > > IMO it's okay to create table in java code. We should document it in > > > operator guide as well as put a log message when we create table. > > > And in case you don't have privileges, the operator should throw > > meaningful > > > message. > > > > > > -Priyanka > > > > > > On Fri, Jan 13, 2017 at 4:07 PM, Yogi Devendra < > yogidevendra@apache.org> > > > wrote: > > > > > > > My suggestions: > > > > > > > > 1. Have a separate utility script for creating this table. > > > > 2. Have README for the utility script > > > > 3. Mention about the utility script in the operator javadocs. > > > > 4. Mention about the utility script in the application README. > > > > 5. If at all, you wish to ease out the process; you can introduce > > flag > > > > like autoPopulateMetaTable. But. default value of this flag should > > to > > > be > > > > off. > > > > 6. I would prefer to avoid side-effects unless explicitly asked by > > the > > > > end user. > > > > 7. Relevant exceptions should be caught and should have a message > > > which > > > > can be understood by the end user. > > > > > > > > ~ Yogi > > > > > > > > On 13 January 2017 at 15:57, Hitesh Kapoor > > > wrote: > > > > > > > > > Hi All, > > > > > > > > > > Currently to use JdbcPOJOInsertOutputOperator, user needs to create > > > > > "dt_meta" table to enforce > > > > > exactly-once processing semantic. If the user fails to create this > > > table > > > > > before launching the application an exception is thrown. > > > > > To handle this scenario we can automate the process of creating > this > > > > table, > > > > > assuming the user has the appropriate privileges. The problem with > > this > > > > > approach is that it may not be a very good idea to modify user's > > > database > > > > > automatically , also if the user doesn't has the appropriate > > privileges > > > > it > > > > > will eventually throw an exception (however a different exception). > > > > > So I need your opinion if we should automate the creation of this > > > > internal > > > > > table (if it doesn't exists) or continue with the existing > behaviour > > or > > > > > anything else. > > > > > > > > > > Regards, > > > > > Hitesh > > > > > > > > > > > > > > > --94eb2c033158e2a2d7054606cae0--