Michel Davit
Michel Davit
Scio does run with avro model defining logical types as defined in the [avro specification](https://avro.apache.org/docs/1.9.2/spec.html#Logical+Types). Avro 1.8 generates broken java code which does not allow full support of the feature...
Prepare scala 3 developpment. Contributors would need to simply run `++3.1.2!` in sbt to start development in scala 3 cross build and CI stay on scala 2 for now
Fix #545 # Modules - [x] avro - [x] bigquery - [x] bigtable - [x] cats - [x] datastore - [ ] docs - [x] guava - [ ] jmh...
fix #564
As for the other modules, `magnolify` should not enforce the `cats` and `scalacheck` version but let the use be in control.
`com.softwaremill.magnolia1_3` is available. Try to see if we can cross-build for scala 3
I'm wondering if we can use the artifact change release to put some breaking changes into `magnolify`. I noticed that depending on the module, the automatic derivation is not always...
As of today, Akka Http only allows using HTTP2 with bindAndHandleAsync method. Since .recordMetrics returns a flow, I can't use this library with HTTP2 which only takes `HttpRequest ⇒ Future[HttpResponse]`...
Beam's new way of writing custom do function is to use annotations in the `@ProcessElement` function. Check that `ProcessContext` is only used where relevant Update to newer beam style when...
setup actions with Java 17. Also check deprecation plan for other JVM versions as some libraries are not backward compatible with Java 8, 11: - [neo4j-java-driver](https://github.com/neo4j/neo4j-java-driver#supported-driver-series)