Nikhil G
Nikhil G
So we don't have to worry about having an exhaustive blacklist of bad/modifying sql statements
Don't want to let user input mess with table permissions on our side. Alternatively, we could just fix this at the session level with ```SET SESSION TRANSACTION READ ONLY;```
* only applicable to maps where zip codes are highlighted (thus far) * could also extend to graphs (e.g. click row -> highlight/select column in bar graph)
### Description Follow-up to #59212. The current `continue_on_error` implementation only handles the case where the vLLM engine runs in the same lifecycle as the Ray Data pipeline (`vLLMEngineStage`). When using...
## Update / streamline batch inference documentation - Include new visuals of updated architecture - Reflect refactor for batch inference config knobs / etc - Simplify user walkthrough and onboarding...