Re: Flink 1.2 Proper Packaging of flink-table with SBT

2017-03-08 Thread Justin Yan
> Jar file, I created a Jira issue (https://issues.apache.org/ > jira/browse/FLINK-5994). This is very strange as it actually a dependency > of flink-table. > > Thanks again for the feedback. If you experience any further issues with > the Table API feel free to post them here. >

Re: Flink 1.2 Proper Packaging of flink-table with SBT

2017-03-07 Thread Justin Yan
the dependencies it requires, and so I'd be curious to hear what the proper procedure is for linking against `flink-table` if you want to avoid the bug I highlighted in the aforementioned JIRA. Thank you and sorry for the extra noise! Justin On Tue, Mar 7, 2017 at 7:21 PM, Justin Yan <jus

Flink 1.2 Proper Packaging of flink-table with SBT

2017-03-07 Thread Justin Yan
Hello! We are attempting to use the Flink Table API, but are running into a few issues. We initially started with our dependencies looking something like this: libraryDependencies ++= Seq( "org.apache.flink" %% "flink-scala" % "1.2.0" % "provided", "org.apache.flink" %% "flink-clients" %

Re: Kinesis Connector Dependency Problems

2016-11-02 Thread Justin Yan
r suspicion? > If the error doesn't occur on a more recent EMR version, then we know why > its happening. > > We'll then probably need to shade (relocate) the Kinesis code to make it > work with older EMR libraries. > > Regards, > Robert > > > On Tue, Nov 1, 2016 at

Re: Kinesis Connector Dependency Problems

2016-11-01 Thread Justin Yan
the classpath > with which the Flink cluster was started on Yarn. You can find this > information at the beginning of your TaskManager log file. Thanks a lot. > > Cheers, > Till > > On Mon, Oct 31, 2016 at 8:22 PM, Justin Yan <justin@remitly.com> > wrote: > >

Kinesis Connector Dependency Problems

2016-10-31 Thread Justin Yan
Hi all - first time on the mailing list, so my apologies if I break protocol on anything. Really excited to be using Flink, and hoping to be active here in the future! Also, apologies for the length of this email - I tried to include details but may have gone overboard. The gist of my problem