On Tue, Mar 10, 2020 at 1:27 AM Elias Djurfeldt <elias.djurfe...@mirado.com> wrote:
> From what I can tell, the only difference is that the Python connector is > a pure Python implementation and doesn't rely on ODBC or JDBC (it's just a > pip installable). Whereas the Java version needs JDBC. But that seems to be > the only difference. > Correct me if I'm wrong, but this sounds like a concern around having to install Java dependencies for the cross-language transform. If so, I think the question is: how frictionless can we make the user experience here? If it can be relatively straightforward, even for a Python user with zero Java familiarity, it's going to be a win from a maintainability perspective to only have one implementation (Java, in this case) to keep up to date, as Cham pointed out. Kasia, do you have a sense yet for what the experience for a Python user would be for using the Python-wrapped Java SnowflakeIO connector? -Tyler > > I don't know enough about the Java side of Beam (or Java in general > really) to say if that's an issue or not though :) > > Cheers, > > On Mon, 9 Mar 2020 at 18:06, Chamikara Jayalath <chamik...@google.com> > wrote: > >> Thank you. Elias and Shashanka, do you think the Python connector (and >> API) can offer some additional benefits that a Java cross-language >> <https://beam.apache.org/roadmap/connectors-multi-sdk/> connector cannot >> ? It's fine to develop Java and Python versions if it makes sense but if >> cross-language Java version offers the same benefits as Python just having >> one implementation will reduce maintenance burden. >> >> Thanks, >> Cham >> >> On Mon, Mar 9, 2020 at 5:41 AM Katarzyna Kucharczyk < >> ka.kucharc...@gmail.com> wrote: >> >>> Hi all, >>> >>> Me and my colleague Dariusz we are working currently on Java connector >>> and we are planning to use cross-language to add Python as well. The >>> proposal should arrive on dev-list in the nearest future. >>> Also we would be happy to help if needed in current work of yours. >>> >>> Cheers, >>> Kasia >>> >>> On Mon, Mar 9, 2020 at 9:41 AM Elias Djurfeldt < >>> elias.djurfe...@mirado.com> wrote: >>> >>>> Cool Shashanka! Feel free to tag me in the JIRA and update me on any >>>> progress / ponderings. >>>> >>>> Cheers, >>>> Elias >>>> >>>> On Sat, 7 Mar 2020 at 03:43, Chamikara Jayalath <chamik...@google.com> >>>> wrote: >>>> >>>>> Absolutely. Please create a JIRA and coordinate with Elias and any >>>>> others that would like to contribute to this. >>>>> >>>>> Thanks, >>>>> Cham >>>>> >>>>> On Fri, Mar 6, 2020 at 10:46 AM Shashanka Balakuntala < >>>>> shbalakunt...@gmail.com> wrote: >>>>> >>>>>> Hi Chamikara and Elias, >>>>>> This seems like an interesting feature. Can I start working on this? >>>>>> *Regards* >>>>>> Shashanka Balakuntala Srinivasa >>>>>> >>>>>> >>>>>> >>>>>> On Sat, Mar 7, 2020 at 12:00 AM Chamikara Jayalath < >>>>>> chamik...@google.com> wrote: >>>>>> >>>>>>> I don't think we have this but contributions are welcome. >>>>>>> >>>>>>> Thanks, >>>>>>> Cham >>>>>>> >>>>>>> On Tue, Mar 3, 2020 at 4:46 AM Elias Djurfeldt < >>>>>>> elias.djurfe...@mirado.com> wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> I've stumbled upon a use case where I might need a SnowflakeIO in >>>>>>>> Python. Has anyone worked on this before or are there any discussions >>>>>>>> surrounding it? >>>>>>>> >>>>>>>> There is a Snowflake Python library available [1], so looks >>>>>>>> feasible to implement in Beam. >>>>>>>> >>>>>>>> [1] >>>>>>>> https://docs.snowflake.net/manuals/user-guide/python-connector.html >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Elias >>>>>>>> >>>>>>>
