• Bolek Ziobrowski

    Bolek Ziobrowski

    7 months ago
    Hi @Orrin . Can you double check table definition to make sure it's the same (esp. around designated timestamp and partitioning ) . Could you also paste the SQL/ csv that you used ?
    Bolek Ziobrowski
    o
    8 replies
    Copy to Clipboard
  • b

    Beetzn

    7 months ago
    Hi, I have a problem concerning queries with timestamp in the where clause. I am using the embedded Java solution. This is the table I have created in my code:
    CREATE TABLE IF NOT EXISTS MESSAGES (type string NOT NULL, timestamp_message TIMESTAMP NOT NULL, data_blob binary NOT NULL) timestamp(timestamp_message) PARTITION BY HOUR WITH maxUncommittedRows=250000, commitLag=240s
    If I query for type it works well and I get the results. If I query for timestamp_message I get no results. I have tried many different ways as described in the docs, e.g query for the year
    SELECT * FROM MESSAGES WHERE timestamp_message in '2022'
    or query for a time range
    SELECT * FROM MESSAGES where timestamp_message between '2022-01-01T00:00:00.000000Z' and '2022-12-01T00:00:00.000000Z
    nothing works. Could you please tell me which is the correct timestamp format? I guess this is the problem...
    b
    Alex Pelagenko
    +1
    11 replies
    Copy to Clipboard
  • o

    Orrin

    7 months ago
    @Nicolas Hourcard et al….. we going to have any upcoming live sessions/conferences etc? (i missed the last live event)
    o
    Pei
    3 replies
    Copy to Clipboard
  • Luiz Otavio

    Luiz Otavio

    7 months ago
    Hello guys, I would like to know if is possible to make o3 commit-lag for days ? or keep it working and schedule routine to reorder everything
    Luiz Otavio
    Alex Pelagenko
    4 replies
    Copy to Clipboard
  • g

    gmaurice

    7 months ago
    Hello, Is someone succeeded to make https://github.com/justwatchcom/sql_exporter working with questdb ? Because I configured
    sql_exporter
    with the good connection string, but it does not want to work with this error message :
    sql_exporter | {"caller":"job.go:197","err":"driver: bad connection","job":"questdb_trades_exchange_freshness","level":"warn","msg":"Failed to connect","ts":"2022-02-20T09:35:55.29991261Z"}
    I guess there is some incompatibility but i’m not sure. In
    sql_exporter
    config file the connection string is very simple and
    sql_exporter
    runs in docker in the same network as
    questdb
    :
    ...
    connections:
      - '<postgres://admin:quest@questdb:8812/qdb?sslmode=disable>'
    ...
    Any piece of advice ?
    g
    Alex Alekseichuk
    5 replies
    Copy to Clipboard
  • Luiz Otavio

    Luiz Otavio

    7 months ago
    Hello guys, I have quick question about distinct.
    Luiz Otavio
    Alex Pelagenko
    9 replies
    Copy to Clipboard
  • Eugene teu

    Eugene teu

    7 months ago
    CREATE table test (
        a long256,
        b long256
    )
    
    insert INTO TEST (a,b) VALUES(0x94a942,0x94a942)
    
    select * from test where a >= 0x94a942;
    hi can i check for this, im not able to use
    >=
    operator for
    long256
    values?
    Eugene teu
    Andrey Pechkurov
    +1
    39 replies
    Copy to Clipboard
  • John Scarrott

    John Scarrott

    7 months ago
    When running some queries we get an error:
    could not open read-only [file=/root/.questdb/db/metrics/2022-01-27T11.86/measurement.k]
    But are unsure how to fix it
    John Scarrott
    Alex Pelagenko
    +1
    6 replies
    Copy to Clipboard
  • David Williams

    David Williams

    7 months ago
    I don't know why Record.getTimestamp(int) returns 0 and a real long value alternately;
    David Williams
    Alex Pelagenko
    +1
    12 replies
    Copy to Clipboard
  • g

    gmaurice

    7 months ago
    Hello, is it possible to downgrade from questdb 6.2 to 6.1.3 without affecting data ?
    g
    Vlad
    +1
    25 replies
    Copy to Clipboard