I will be extra transparent here: we’re in an alpha, and generally don’t share timelines about beta
I will be extra transparent here: we’re in an alpha, and generally don’t share timelines about beta or GA steps, because they almost always lead to disappointment. A beta or GA isn’t just a checklist of features: it’s about ensuring we have observed the system to be reliable in the hands of users. This is especially true for a database product.
Further, when we land the new storage subsystem, we fully expect (we have validated internally, in fact) for these transient query failures to go away. They are an outcome of how we shipped an early alpha — so that users can play with D1 and provide feedback on the rest of the experience — versus holding off until we landed the storage layer we intend to build on proper
Further, when we land the new storage subsystem, we fully expect (we have validated internally, in fact) for these transient query failures to go away. They are an outcome of how we shipped an early alpha — so that users can play with D1 and provide feedback on the rest of the experience — versus holding off until we landed the storage layer we intend to build on proper

