Jaromir Hamala

something like `!CST` looks ok first. but if you think about it: 1. it makes `!` a special character - it means compatibility issues. 2. the same patterns is used...

hello @jsaathof, are you sure QuestDB sends the redirect? Isn't your browser being too keen on trying HTTPS on its own? Since I am unaware of QuestDB ever sending a...

hello @Dapeng960208, can you please clarify what's the expected behaviour vs. the behaviour you observe? it's not very clear what you are trying to achieve.

I learned from @insmac that's the asset path as [documented here](https://questdb.io/docs/develop/web-console/#providing-an-asset-path) is actually a build-time option, not a runtime option. So making this configurable for end-users will need changes in...

This [was fixed](https://github.com/questdb/ui/pull/299) in the latest web console and the next QuestDB version will include this change. This means it'll be possible to have an ingress_controller / reverse_proxy where QuestDB...

> providing a config option is relatively low impact long term I know @bluestreak01 has a different view, but I disagree with this sentiment. Config options are evil! :) Each...

I can agree with that :)

the `SampleByInterpolateRecordCursorFactory` is not aware of alignment at all. Unlike other implementations of `SampleBy*RecordCursorFactory` it does not accept ``` timezoneNameFunc, timezoneNameFuncPos, offsetFunc, offsetFuncPos ``` as parameters.

@nwoolmer Did you consider benchmarking it? I’d assume functions in `Timestamps` can often be on a hot-path (flooring timestamps for every row). e.g. `getTimeMicros()` The code is now more complex...

@nwoolmer how would you define semantic of `Timestamp.floorXY()` when `offset > micros` ?