users-public
  • Nicolas Hourcard

    Nicolas Hourcard

    11/24/2022, 12:05 PM
    Another fantastic article from @Kovid Rathee on our SQL time series extensions! There is a lot on SAMPLE BY, check it out: https://questdb.io/blog/2022/11/23/sql-extensions-time-series-data-questdb-part-ii
  • Nicolas Hourcard

    Nicolas Hourcard

    11/24/2022, 1:18 PM
    and welcome @Bouarfa Mahi and @Ian Massingham! nice to meet you, we’d love to learn more about what you’re building with QDB
  • b

    Bouarfa Mahi

    11/24/2022, 2:44 PM
    hey, @Nicolas Hourcard i am a quant and searching for deeply hidden secrets in Time Series. I have worked with JuliaDB for 3 years and just switched to Questdb. Easy to install and use on jupyterhub with the Julia kernel. Thanks for these well done tutorials.
  • a

    Arka Prabha Roy

    11/24/2022, 2:53 PM
    Hey, do Questdb send swags internationally via UPS?
  • j

    javier ramirez

    11/24/2022, 3:06 PM
    Hey @Ian Massingham. Great to see you here 🙂
  • Nicolas Hourcard

    Nicolas Hourcard

    11/24/2022, 7:01 PM
    welcome @Aaditya Champaneri and @Akash R Chandran!
  • a

    Antonio Jimenez

    11/25/2022, 9:49 AM
    👋 Hello, team!
  • Nicolas Hourcard

    Nicolas Hourcard

    11/25/2022, 9:53 AM
    hey @Antonio Jimenez , nice to meet you
  • Miguel Arregui

    Miguel Arregui

    11/25/2022, 10:10 AM
    buenos dias community!!!
  • a

    Antonio Jimenez

    11/25/2022, 10:13 AM
    👋
  • a

    Antonio Jimenez

    11/25/2022, 3:34 PM
    Hello again! I'm playing a little with questdb, and I think I've found a bug (or limitation with CentOs). I've downloaded the version: questdb-6.6.1-rt-linux-amd64.tgz. And started with:
    ./questdb.sh start -d /tmp
    I've create several tables using the WebConsole, and the tables doesn't appears on the lateral menu, but the problem can be reproduce using the "curl" command. Just started no tables are retrieved:
    curl -G --data-urlencode "query=show tables" http://localhost:9000/exp
    "table"
    curl -G --data-urlencode "query=CREATE TABLE IF NOT EXISTS Testing(id INT, name STRING)" http://localhost:9000/exec
    {"ddl":"OK"} Not after create Testing.
    curl -G --data-urlencode "query=show tables" http://localhost:9000/exp
    "table" And no describing.
    curl -G --data-urlencode "query=describe Testing" http://localhost:9000/exp
    {"query":"describe Testing","error":"table does not exist [table=describe]","position":0} But the table seems to be created into the db folder:
    -rw-r--r--. 1 0 nov 25 16:21 Testing.lock
    -rw-r--r--. 1 4096 nov 25 16:21 _tab_index.d
    drwxrwxr-x. 3 88 nov 25 16:21 Testing
    All of this was executed in a CentOS Linux release 7.2.1511; and the starting log returns this suspicious trace. "A server-main - db root: [path=/tmp/db, magic=0x58465342] -> UNSUPPORTED (SYSTEM COULD BE UNSTABLE)" Sorry if this channel is not for that! 😅
  • a

    Antonio Jimenez

    11/25/2022, 3:43 PM
    The file system is xfs.
  • t

    theseusyang

    11/26/2022, 8:14 AM
  • t

    Thomas Webster

    11/27/2022, 11:30 AM
    Hi all, thanks questdb team, a great improvement over my previous setup. Currently using for an hft/marketmaking operation. Encountered a slight issue, when querying with postgres wire protocol I'm finding float data type columns being rounded to 3 decimal places. Cairo.sql.float.cast.scale and http.json.query.float.scale are both set to high dp - however i cannot find a similar option for postgres. Any ideas? Cheers all.
  • Nicolas Hourcard

    Nicolas Hourcard

    11/27/2022, 8:06 PM
    welcome @Osvaldo
  • Andy

    Andy

    11/28/2022, 6:01 AM
    the version 6.61 is not stable ,the status of qdb frequently be inactive ,there are two crash logs, my questdb is on windows11 os
  • k

    Kevin Burkhardt

    11/28/2022, 7:45 AM
    Hi there -- I'm new to QuestDB and looking for guidance on how to approach the following: given a dataset of user activity like: timestamp,event_id,email,action 2022-11-20T18:44:47.376Z,1,john.doe@domain.com,login 2022-11-20T18:51:10.998Z,2,john.doe@domain.com,run report 2022-11-20T18:58:10.998Z,3,john.doe@domain.com,logout 2022-11-20T21:41:47.376Z,4,john.doe@domain.com,login 2022-11-20T21:42:41.376Z,5,john.doe@domain.com,run report 2022-11-20T21:45:41.376Z,6,john.doe@domain.com,logout I want to find the users who have been idle (or logged out) for more than a certain amount of time in a given day (e.g. > 1hr). ie. where time interval between logout/login events > 1hr (and/or time interval between any 2 successive events > 1hr). Thanks in advance for any pointers
  • p

    Petr Postulka

    11/28/2022, 9:07 AM
    hi everybody, any chance to remove the following drawback of questdb? Is it difficult or relatively straightforward task? https://github.com/questdb/questdb/issues/2550
  • Nicolas Hourcard

    Nicolas Hourcard

    11/28/2022, 11:02 AM
    Hi <!here> We have just released a new version, which introduces dynamic commits. This way, we abstract the commit lag configuration away from our users, and QuestDB will always find the optimal mix between data availability (“freshness”) for reads and out of order data ingestion throughput. We go through the story behind this feature, and why it became a pain point for new users to configure the commit lag. This is now a thing of the past! Hope you find this useful, and shout out to our community for their contributions! https://questdb.io/blog/2022/11/25/questdb-6.6.1-dynamic-commits/
  • j

    javier ramirez

    11/29/2022, 9:07 AM
    Welcome to our slack, @Olena Pelagenko, @Srinivas A.K, and @poojitha pullambhatla. If you want to share how you are using QuestDB or if you have any questions, we’ll be happy to hear from you. Of course it is totally fine if you prefer just to read the slack to get a feeling of the community without actively engaging 🙂
  • Newskooler

    Newskooler

    11/29/2022, 9:54 AM
    Anyone else needs this, please vote 👍 in GitHub:https://github.com/questdb/questdb/issues/2830
  • Nicolas Hourcard

    Nicolas Hourcard

    11/29/2022, 9:58 AM
    welcome @JM !
  • j

    JM

    11/29/2022, 10:07 AM
    Thanks @Nicolas Hourcard 🙂
  • j

    JM

    11/29/2022, 10:21 AM
    I actually come with a question/problem. I implemented QuestDB for a customer to monitor Airflow via statsd/Telegraf + Grafana. It is all running smoothly, and there are no problems regarding the performance. However, on the side of browseability, I have no way to see, what tables I have in the database. tables() is empty, the browser does not display anything either, but the tables created by the influx line protocol do exist and have data Version: 6.5.4 Set up via the official Docker Image If there is more info required I am happy to provide.
  • a

    Ajay Pilaniya

    11/29/2022, 1:39 PM
    Over last one month we have performed some load tests around many timeseries databases and QuestDB has outperformed every database. At our organization we have decided to go ahead with QuestDB for our analytics framework. I would like to thank @Andrey Pechkurov who helped us around some setup issues and helped us understand QuestDB core concepts.
  • a

    Ajay Pilaniya

    11/29/2022, 1:43 PM
    We have started the integration today and since currently we don’t have much write heavy load we are using PGWire in JAVA using JPA. One issue we are facing is that our service had integrated spring batch and spring batch tries to store meta data regarding any batch jobs using JPA but since quest db uses different dialect when it comes to create table queries, our service won’t start giving below error :
    Caused by: org.postgresql.util.PSQLException: ERROR: found [tok='(', len=1] ',' or ')' expected
    This error is generated when spring batch framework tries to create a new table for it’s usage using PGWire. This is also happening for QuestDB tables but currently I am manually creating them but since I am not aware of spring batch table schemas, is there any workaround this?
  • Nicolas Hourcard

    Nicolas Hourcard

    11/29/2022, 5:31 PM
    welcome @dean licheri