Hello! I don't think there is this particular example but you can frankenstain it from existing ones. If you have any troubles then you can share your project for us to see.
Otherwise you can indeed use SET STREAMING and avoid trouble. There is extra time and space considerations when using secondary indexes but otherwise there is no overhead. Regards, -- Ilya Kasnacheev вт, 19 февр. 2019 г. в 13:44, Clay Teahouse <[email protected]>: > Thank you for the replies. > Any example, with using a cache template for creating the tables and using > the streamer API to load the table? > Also, one more thing: is there a performance penalty for using the > relational structure imposed on the data, as opposed to manipulating the > java objects directly? If no, what is the most optimized way of populating > and accessing the tables? > > thank you again > Clay > > On Tue, Feb 19, 2019 at 3:11 AM Stephen Darlington < > [email protected]> wrote: > >> Ignite comes with a nice sample for using the Data Streamer API: >> https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/streaming/StreamTransformerExample.java >> >> >> There’s nothing really “special” about caches/tables created using DDL >> rather than one of the other methods. >> >> Regards, >> Stephen >> >> On 19 Feb 2019, at 03:49, Clay Teahouse <[email protected]> wrote: >> >> Hello All, >> >> Can someone share an example of utilizing IgniteDataStreamer API to >> populate a table created via a DDL? >> >> thank you, >> Clay >> >> >> >>
