Mailing-List: contact users-help@apex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@apex.apache.org
MIME-Version: 1.0
From: "hsy541@gmail.com" <hsy541@gmail.com>
Date: Wed, 6 Jul 2016 10:17:30 -0700
Message-ID: <CAG2CJAd3-yzC3k1vikmWGTXx_C2mnsJV25purTkdAkaXbpdCtQ@mail.gmail.com>
Subject: Questions about dag validation
To: users@apex.apache.org
Content-Type: multipart/alternative; boundary=94eb2c11bd869c120f0536fabe46
archived-at: Wed, 06 Jul 2016 17:17:37 -0000

--94eb2c11bd869c120f0536fabe46
Content-Type: text/plain; charset=UTF-8

Hey guys,

I've a problem using jdbc output operator. It is same as
http://stackoverflow.com/questions/37887390/datatorrent-jdbcoperator-not-workiing

After trouble shooting, I found there might be some validation issue here
that prerun validation for dag won't work in some special case

Here is an example, let's say we have an Operator

class MyOperator<B extends MyBean> implements Operator {

   B b;

}

class MyBean {
 @NotNull
 cantBeNullProp

 setCan...

 getCan...

...
}

If user forget to set the cantBeNullProp Property, prerun validation won't
pick it.

Is it a limitation of javax validation or we can do better to support this
kind of validation?

Regards,
Siyuan

--94eb2c11bd869c120f0536fabe46
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div>Hey guys,<br><br></div>I&#39;ve a=
 problem using jdbc output operator. It is same as <br><a href=3D"http://st=
ackoverflow.com/questions/37887390/datatorrent-jdbcoperator-not-workiing">h=
ttp://stackoverflow.com/questions/37887390/datatorrent-jdbcoperator-not-wor=
kiing</a><br><br></div>After trouble shooting, I found there might be some =
validation issue here that prerun validation for dag won&#39;t work in some=
 special case<br><br></div>Here is an example, let&#39;s say we have an Ope=
rator<br><br></div>class MyOperator&lt;B extends MyBean&gt; implements Oper=
ator {<br></div>=C2=A0<br>=C2=A0=C2=A0 B b;<br><br><div>}<br><br></div><div=
>class MyBean {<br></div><div>=C2=A0@NotNull<br></div><div>=C2=A0cantBeNull=
Prop<br><br></div><div>=C2=A0setCan...<br><br></div><div>=C2=A0getCan...<br=
></div><div><br>...<br></div><div>}<br><br></div><div>If user forget to set=
 the cantBeNullProp Property, prerun validation won&#39;t pick it.<br><br><=
/div><div>Is it a limitation of javax validation or we can do better to sup=
port this kind of validation?<br><br></div><div>Regards,<br></div><div>Siyu=
an<br></div></div>

--94eb2c11bd869c120f0536fabe46--