You can just use plain JDBC. Just keep in mind, that the classes will be serialized and sent through the cluster. So probably, you want to initialize all the non-serializable database access object in the open method itself (as opposed to the constructor (client side)).
Cheers, Konstantin On 12.09.2016 13:53, Philipp Bussche wrote: > Thank you Konstantin, the amount of data I have to load into memory will be > very small so that should be alright. > When opening and querying the database would I use any sort of Flink magic > or just do plain JDBC ? > I read about the JDBCInput concept which one could use with the DataSet API > and was wondering if I could use that somehow in my open method then ? > > Thanks > Philipp > > > > -- > View this message in context: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Enriching-a-tuple-mapped-from-a-datastream-with-data-coming-from-a-JDBC-source-tp8993p9002.html > Sent from the Apache Flink User Mailing List archive. mailing list archive at > Nabble.com. > -- Konstantin Knauf * konstantin.kn...@tngtech.com * +49-174-3413182 TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterföhring Geschäftsführer: Henrik Klagges, Christoph Stock, Dr. Robert Dahlke Sitz: Unterföhring * Amtsgericht München * HRB 135082
signature.asc
Description: OpenPGP digital signature
