Satyam Singh

i want to be added on the list too, you can use my full name and email. `Satyam Singh `

I tested for this by tracing on two different MinIo instances. This is what request looks like on local minio instance ``` 127.0.0.1:9000 [REQUEST s3.PutObject] [2022-08-31T13:16:20.401] 127.0.0.1:9000 PUT /logstorage/teststream1/.schema?x-id=PutObject 127.0.0.1:9000...

@kmartin62 Sorry for inconvenience. After one of my recent PR this has changed to `Bad request: Error parsing query: Stream is not initialized yet. Post an event first`. This is...

> > Error types for now compose upwards the call stack. The type is QueryError::Parse(ParseError::Validation(QueryValidationError)) > > Can you link to this in the repo. [here](https://github.com/parseablehq/parseable/blob/dd24e091eaa1399384a1171b6e9d34143eb1b3fb/server/src/validator.rs#L155-L157) also mentioned in #147

> 1. Incorrect alert field causes server to panic. Alert config field should be checked at time of registering alert. I will add that to validation. It does not make...

@stanvanrooy Can you tell us which version of parseable you are running.

@Skryabind I recognize this error because we have ran into this couple of times. I created an issue for this while back over here. https://github.com/apache/arrow-datafusion/issues/5706 I need to check though...

@Skryabind Yeah unfortunately this **exact** json won't work with Parseable as of today. The data is very nested with chain of struct of list of structs. We use parquet as...

@stanvanrooy I'll look into fixing this for upcoming release. The parsing for stream name is what is causing this issue. This stream name is used for file selection and query...

@nitisht No