You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a python user, I want no confusion about which method does what.
We should attach a property to every wrapper function to hold the name of the wrapped Java static method.
This will allows for no confusion for the user with the difference between lower_bin and lowerBin and having to know when to use which.
Something akin to an alias so theMethod in Java can be the_method when used from python.
This issue was highlighted with @jcferretti from the Debezium Python V2 rewrite. As there are two ways for the same task ['received_at_minute = lowerBin(received_at, minute_in_nanos)']
As a python user, I want no confusion about which method does what.
We should attach a property to every wrapper function to hold the name of the wrapped Java static method.
This will allows for no confusion for the user with the difference between
lower_bin
andlowerBin
and having to know when to use which.Something akin to an alias so
theMethod
in Java can bethe_method
when used from python.This issue was highlighted with @jcferretti from the Debezium Python V2 rewrite. As there are two ways for the same task
['received_at_minute = lowerBin(received_at, minute_in_nanos)']
['received_at_minute = (DateTime)lower_bin(received_at, minute_in_nanos)']
Linked to #2303
The text was updated successfully, but these errors were encountered: