4 ms·

Awesome no driver changes.

by dkhenry 13y ago

coffeemug 13y ago
For all the driver devs out there, there should be no more driver protocol changes until we hit an LTS release (unless we find some critical API bugs that need to be fixed).
- TylerE 13y ago
  With that being the case are there plans to spend a bit more time on driver support? At the very least a high-quality 1st party Java driver would go a long way. Even better if you provide Scala/Clojure/Groovy bindings.
  - coffeemug 13y ago
    Our goal is to get to an LTS release without increasing the surface area of the project. Once the LTS release is out, we'll likely take on critical community projects under our roof and offer first-class support for them. This should start happening in the next couple of months. (Unfortunately until we get to LTS we don't quite have the resources to support new drivers)
  - dabeeeenster 13y ago
    Can anyone comment on the quality of the 3rd party Java driver (https://github.com/dkhenry/rethinkjava https://github.com/dkhenry/rethinkjava)?
    - dkhenry 13y ago
      I am biased, but It is a very straight forward implementation building directly on the protobuf interface. It lacks some of the niceties of the interperted drivers, but It is as fast as ( or faster in some cases ) then the official drivers ( as best I can tell ) The author stopped working on it for a little because he was tired of refactoring his code as the protocol changed and figured he would just add all the missing bits once they finished the protocol.
      - tigeba 13y ago
        I was eager to give these a whirl but from my perspective the AGPL licensing is rather onerous considering that the official drivers are APL. Not sure if this was intentional or accidental.
        dkhenry 13y ago
        Well Color me surprised. Your right. I just used the same license that RethinkDB is licensed under, I didn't see that they had the drivers under a different license. By Tomorrow I will have them updated to APL ( luckily I can do this since no one else has really supplied a pull request :-( )
        tigeba 13y ago
        Excellent! I will check them out and send off a pull request if I run into anything.
        mglukhovsky 13y ago
        The official RethinkDB drivers are licensed as Apache 2 (see https://github.com/rethinkdb/rethinkdb/blob/next/drivers/COPYRIGHT https://github.com/rethinkdb/rethinkdb/blob/next/drivers/COP...), whereas the server is licensed under AGPL. We strongly recommend all community drivers use a less restrictive license like Apache 2 (or other license of choice). Also: dkhenry, thanks for all your hard work in helping bring RethinkDB to the Java community!

Awesome no driver changes.

by dkhenry 13y ago

Awesome no driver changes.

For all the driver devs out there, there should be no more driver protocol changes until we hit an LTS release (unless we find some critical API bugs that need to be fixed).

TylerE 13y ago
With that being the case are there plans to spend a bit more time on driver support? At the very least a high-quality 1st party Java driver would go a long way. Even better if you provide Scala/Clojure/Groovy bindings.
- coffeemug 13y ago
  Our goal is to get to an LTS release without increasing the surface area of the project. Once the LTS release is out, we'll likely take on critical community projects under our roof and offer first-class support for them. This should start happening in the next couple of months. (Unfortunately until we get to LTS we don't quite have the resources to support new drivers)
- dabeeeenster 13y ago
  Can anyone comment on the quality of the 3rd party Java driver (https://github.com/dkhenry/rethinkjava https://github.com/dkhenry/rethinkjava)?
  - dkhenry 13y ago
    I am biased, but It is a very straight forward implementation building directly on the protobuf interface. It lacks some of the niceties of the interperted drivers, but It is as fast as ( or faster in some cases ) then the official drivers ( as best I can tell ) The author stopped working on it for a little because he was tired of refactoring his code as the protocol changed and figured he would just add all the missing bits once they finished the protocol.
    - tigeba 13y ago
      I was eager to give these a whirl but from my perspective the AGPL licensing is rather onerous considering that the official drivers are APL. Not sure if this was intentional or accidental.
      - dkhenry 13y ago
        Well Color me surprised. Your right. I just used the same license that RethinkDB is licensed under, I didn't see that they had the drivers under a different license. By Tomorrow I will have them updated to APL ( luckily I can do this since no one else has really supplied a pull request :-( )
        tigeba 13y ago
        Excellent! I will check them out and send off a pull request if I run into anything.
      - mglukhovsky 13y ago
        The official RethinkDB drivers are licensed as Apache 2 (see https://github.com/rethinkdb/rethinkdb/blob/next/drivers/COPYRIGHT https://github.com/rethinkdb/rethinkdb/blob/next/drivers/COP...), whereas the server is licensed under AGPL. We strongly recommend all community drivers use a less restrictive license like Apache 2 (or other license of choice). Also: dkhenry, thanks for all your hard work in helping bring RethinkDB to the Java community!