Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use cascading.tuple.Tuple's getObject method instead of get. #48

Merged
merged 1 commit into from
Jan 7, 2014
Merged

Use cascading.tuple.Tuple's getObject method instead of get. #48

merged 1 commit into from
Jan 7, 2014

Conversation

mishok13
Copy link
Contributor

@mishok13 mishok13 commented Jan 7, 2014

The latter is deprecated and does a cast to java.lang.Comparable which
means that some data types can not be used with Maple's
JDBCTap (e.g. primitive arrays, org.postgresql.util.PGObject, etc).

The latter is deprecated and does a cast to java.lang.Comparable which
means that some data types can not be used with Maple's
JDBCTap (e.g. primitive arrays, org.postgresql.util.PGObject, etc).
johnynek added a commit that referenced this pull request Jan 7, 2014
Use cascading.tuple.Tuple's getObject method instead of get.
@johnynek johnynek merged commit 96c3017 into Cascading:develop Jan 7, 2014
@johnynek
Copy link
Contributor

johnynek commented Jan 7, 2014

Looks like this is already fixed in cascading-jdbc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants