GitHub user gilcesarf opened a pull request:
https://github.com/apache/storm/pull/1936
STORM-2354: Upgrade to datastax driver 3.1.3
implemented some fixes to allow using driver 3.1.3.
This TODO is also commented in the code as a possible new fix:
// TODO: codecFor(Object) return first codec that accepts value.
// perhaps we could provide a way to the programmer give more info
// to allow other forms of codedFor more suitable to the case we
// known the the correct CSQL types involved. Anyway, does not
// impact when Token-aware Load Balancing Policy is not used.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gilcesarf/storm
upgrade_to_datastax_driver_3.1.3
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1936.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1936
----
commit 53f7955a1168eefd58200c01307761d34d8457b4
Author: Gil Cesar Faria <[email protected]>
Date: 2017-02-08T15:19:05Z
upgrade to version 3.1.3 of datastax driver
commit 313825e71597728c916c15ffcca9e63da1c9902b
Author: Gil Cesar Faria <[email protected]>
Date: 2017-02-08T18:20:56Z
- Changed from setDate(String, Date) to setTimestamp(String, Date) since
setDate(String, Date) was deprecated and removed from API.
commit 240eefa1d31801a10de0b631a196ec5352dbd47d
Author: Gil Cesar Faria <[email protected]>
Date: 2017-02-08T18:29:40Z
Added support for default CodeRegistry/TypeCodec instead of deprecated
DataType serialize method.
TODO: codecFor(Object) return first codec that accepts value.
Perhaps we could provide a way to the programmer give more info to allow
other forms of codedFor more suitable to the case we known the the
correct CSQL types involved. Anyway, does not impact when Token-aware
Load Balancing Policy is not used.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
