Vlad Ilyushchenko

This PR is bourn out of releasing QuestDB to maven central. They require javadoc. With each release out warnings grew and sometimes we fell into habit of not maintaining existing...

JDK 17 killed it actually, they generate this as a "warning", doh: ``` [WARNING] Generating C:\Users\Vlad\dev\questdb\core\target\apidocs\io.questdb\io\questdb\std\str\class-use\DirectByteCharSequence.Factory.html... ```

JDK17 onwards wants all public interfaces to be documented, if not - there will be warnings. This PR is on hold until there is good time to revisit this

Crazy, it was a good intention totally spoiled by Java's rigidity

Are you using XFS in production?

thank you! We need to make sure QuestDB runs on XFS. I just ran regression tests and the following test hang: ``` 022-07-25T20:07:14.709082Z I i.q.c.RecoverVarIndex write complete. Index file length:...

To help us understand broader use case and clear assumptions, do you mind providing an example of `string_agg` in a SQL that `SELECT DISTINCT value from table` cannot substitute ?

Thank you @kallewesth sure, @KevinChen16 you can have a go! My concern is with limits, what if there is 1M distinct values? We might need to restrict the implementation from...

JIT is limited to AVX2 amd64 architecture, does not yet work on ARM. That said, database does run on ARM, but without JIT

Can it be cache?