Phillip Webb
Phillip Webb
[ML] Enhancements to `ml.allocated_processors_scale` for increased flexibility in model allocations.
In Spring Framework 5.1 you'll be able to use `WebClient` without Netty which may solve one of the main use cases. I'm tempted to say we should do nothing until...
[ML] Enhancements to `ml.allocated_processors_scale` for increased flexibility in model allocations.
Unfortunately I don't think that's an option since we need to make the decision about what `ApplicationContext` to create before the context is populated with bean definitions.
[ML] Enhancements to `ml.allocated_processors_scale` for increased flexibility in model allocations.
That's certainly still an option. I guess we were hoping that using `WebClient` without Netty was going to become the recommended approach for client only applications.
[ML] Enhancements to `ml.allocated_processors_scale` for increased flexibility in model allocations.
I'll move this back to backlog and think about it some more.
[ML] Enhancements to `ml.allocated_processors_scale` for increased flexibility in model allocations.
I'm not very keen to use the starter alone as an indication. I'd rather we keep starters purely as dependencies.
Unfortunately we're going to need quite a few upstream changes to support this. We've got `LocalContainerEntityManagerFactoryBean` for JPA, `SessionFactory` for Neo4J and `CassandraEntityClassScanner` for Cassandra. @mp911de What would be some...
We'll have another look at this to see how tricky it might be.
Ergh. I think we should push this back then. It's not too urgent for 2.2.x
We discussed this today and we wondered if using the existing mechanisms in Logback would work for you? You can add a `META-INF/services/ch.qos.logback.classic.spi.Configurator` file that references a `Configurator` implementation which...
It'll call the setter if it has one, but it doesn't need one as it'll mutate the existing `List`, `Set` etc. You do need a setter for array types.