Jeremy Kong
Jeremy Kong
The version renders as `unspecified`. This affects internal workflows for jar publishing.
Currently if publish flakes with _some_ artifacts being published, it's rather annoying: 1. Releasing the same commit has been done in the past, but this seems a bit shady and...
In PDS-93832, we observe that TimeLock is able to get into a state where nodes are able to exchange pings, but clients are unable to actually have any client requests...
See PDS-92137. The key graph is the one where successes suddenly stop, there is a small bunch of errors, and then complete silence.
Consider the schema ```java schema.addTableDefinition("table", new TableDefinition() {{ rowName(); rowComponent("row", ValueType.STRING); columns(); column("column", "c", JPersister.class); }}); ``` Produces generated code ```java public SomeType getColumn() { byte[] bytes = row.getColumns().get(PtBytes.toCachedBytes("c")); if...
Currently, the implementation of the bytes hydrator for a user-specified persister is to create a new instance of the persister on each hydration, and then decompress the values. This leads...
Internal reference: PDS-92632 Need to be careful with this one. Quoting my comment on the ticket, > 1. The mechanics of blacklisting in AtlasDB are that requests will be routed...
There was an irregularity in how transactions and the coordination service work for users of these key-value services, which was exposed in #4070. Specifically: > (having transaction versions and the...
Atlas clients support live reloading to a 0 node configuration. The reason 0 node configurations are _allowed_ is because we do need to support this in certain internal workflows, but...
The original implementation of the coordination store didn't worry about cleanup, because it was expected that the number of values written would be very small (a new value was supposed...