That being said, from a business point of few, making Go code base be as close as possible to Java version makes a lot of sense.
Java client is written the way it is. It already shipped and is used by people. Breaking its API was out of the question.
RavenDB is 10 years old and will most likely be here for the next 10 years.
In those future years, both Java client and Go client will have to be evolved to provide access to new capabilities of the server.
The closer the two code bases are, the less effort it takes to maintain those code bases.
That being said, from a business point of few, making Go code base be as close as possible to Java version makes a lot of sense.
Java client is written the way it is. It already shipped and is used by people. Breaking its API was out of the question.
RavenDB is 10 years old and will most likely be here for the next 10 years.
In those future years, both Java client and Go client will have to be evolved to provide access to new capabilities of the server.
The closer the two code bases are, the less effort it takes to maintain those code bases.