https://linen.dev logo
Join SlackCommunities
Powered by
# general
  • s

    Slackbot

    07/13/2023, 5:18 AM
    This message was deleted.
    s
    j
    • 3
    • 5
  • k

    Kumar Saket

    07/13/2023, 3:25 PM
    Hi team, do we support relative time for native queries in druid? I see a discussion going on here - https://github.com/apache/druid/issues/6023
  • s

    Slackbot

    07/13/2023, 4:26 PM
    This message was deleted.
    s
    f
    c
    • 4
    • 5
  • s

    Slackbot

    07/14/2023, 12:48 AM
    This message was deleted.
    b
    d
    • 3
    • 2
  • s

    Slackbot

    07/14/2023, 1:13 PM
    This message was deleted.
    s
    a
    k
    • 4
    • 5
  • s

    Slackbot

    07/15/2023, 1:18 AM
    This message was deleted.
    a
    m
    • 3
    • 2
  • j

    jp

    07/17/2023, 3:35 AM
    Hi everyone, I have question about per-segment caching. In document it says:
    Copy code
    GroupBy v2 queries do not support any caching on broker.
    If so, can GroupBy v2 queries cached on historical?
  • s

    Slackbot

    07/17/2023, 5:06 AM
    This message was deleted.
    j
    • 2
    • 1
  • s

    Slackbot

    07/17/2023, 7:07 AM
    This message was deleted.
    k
    h
    • 3
    • 4
  • a

    Avishek Gurung

    07/17/2023, 8:00 AM
    #C0303FDCZEZ Hi Team, I would like to request your help in finding a solution to the problem that I am facing on using Druid. I am using druid to store the order related information (sample data attached). For any given date range (start and end date), I need to find two important things 1. The distinct number of new customers 2. The distinct number of repeated customers The new customers are basically the ones that have never ever made a purchase. And the repeated customers are the ones that have made previous purchase. Since, the data volume is huge, I cannot query every row and hence, was thinking of rolling up datasource on day wise and use theta-sketches. Now for a given date range, I can find the new customer by dividing the whole data set into two and taking the 'not' of them. Eg, If A is the theta of all customers before the date range and B is the theta of all the customers in the date range, then B-A will give me the result. However, I am not being able to use similar kind of an approach for a repeated customer. Eg, if a customer C1 makes multiple purchase in the selected date range, then this customer should be treated as new as well as repeatable. How can we solve this using Theta. If not Theta, how can we solve it using Druid?
  • s

    Slackbot

    07/17/2023, 8:03 AM
    This message was deleted.
    h
    a
    s
    • 4
    • 3
  • s

    Slackbot

    07/17/2023, 8:15 AM
    This message was deleted.
    s
    • 2
    • 1
  • s

    Slackbot

    07/17/2023, 8:45 AM
    This message was deleted.
    j
    • 2
    • 1
  • s

    Slackbot

    07/17/2023, 3:13 PM
    This message was deleted.
    s
    • 2
    • 1
  • h

    Harsh Upparwal

    07/17/2023, 3:14 PM
    still desired changes are not getting reflected. need help
  • s

    Slackbot

    07/18/2023, 1:13 PM
    This message was deleted.
    d
    j
    a
    • 4
    • 5
  • a

    Anshul Mishra

    07/19/2023, 10:14 AM
    hey, is there an ansible role available for installing the latest druid version?
  • s

    Slackbot

    07/19/2023, 3:21 PM
    This message was deleted.
    d
    s
    s
    • 4
    • 4
  • a

    Abhishek Agarwal

    07/20/2023, 5:20 AM
    https://github.com/apache/druid/pull/14602 - In Druid 27, you will be able to visualize the data in the web console itself. Pretty cool @Vadim
    ❤️ 3
    🔥 12
    🙌 4
  • s

    Slackbot

    07/20/2023, 11:37 AM
    This message was deleted.
    a
    a
    • 3
    • 3
  • s

    Slackbot

    07/20/2023, 5:30 PM
    This message was deleted.
    s
    j
    • 3
    • 8
  • s

    Slackbot

    07/20/2023, 6:53 PM
    This message was deleted.
    e
    a
    • 3
    • 2
  • s

    Slackbot

    07/20/2023, 11:24 PM
    This message was deleted.
    j
    e
    • 3
    • 3
  • s

    Slackbot

    07/21/2023, 8:57 AM
    This message was deleted.
    a
    a
    • 3
    • 2
  • s

    Slackbot

    07/21/2023, 9:53 AM
    This message was deleted.
    k
    a
    • 3
    • 2
  • s

    Slackbot

    07/21/2023, 12:52 PM
    This message was deleted.
    k
    j
    +2
    • 5
    • 6
  • v

    Vamsi Gandrapu

    07/21/2023, 8:28 PM
    We have a multitenant Druid cluster. We have a requirement to enable sse-c for a specific tenant objects, and our data is already partitioned by tenantId. However, we have common s3 configuration for the cluster. How do we go about configuring
    druid.storage.sse.custom.base64EncodedKey
    with tenant specific key? Is historicals tiering an option here ?
  • s

    Slackbot

    07/22/2023, 8:55 AM
    This message was deleted.
    j
    a
    +2
    • 5
    • 5
  • a

    Avishek Gurung

    07/23/2023, 4:59 AM
    Hi #C0303FDCZEZ / Team, Here I am again seeking help. Apologies if I am spamming this group. I have setup a Druid Cluster of 2 brokers and 12 historical, where each Historical is of size 64 core and 256 Gb Ram. I have also optimised the cluster as per the Druid Doc set the processing threads to 63 (64-1). Even for a worst case scenario, I should be able to handle atleast 63 concurrent requests. I am just Jmeter to load test the cluster. I have a heavy query that takes 1.5s to execute. When I fire this query repeatedly with concurrency as 10, the latency goes up to 7-8 seconds. What should I do to tune this cluster?
  • s

    Slackbot

    07/23/2023, 6:41 AM
    This message was deleted.
    j
    g
    • 3
    • 5
1...262728...35Latest