https://pinot.apache.org/ logo
Join Slack
Powered by
# general
  • k

    Kishore G

    11/13/2019, 5:06 AM
    Ah I think I got it.
  • k

    Kishore G

    11/13/2019, 5:07 AM
    But will be beneficial for others to explain the scenario
  • s

    Sandeep Nayak

    11/13/2019, 5:20 AM
    @User just trying to understand whether Pinot would be able to handle such a scenario or would it cause problems
  • k

    Kishore G

    11/13/2019, 5:21 AM
    I can’t think of any reason why that would be an issue.
  • k

    Kishore G

    11/13/2019, 5:21 AM
    @User wdyt
  • m

    Mayank

    11/13/2019, 5:22 AM
    Yeah, agree. One callout is that we don't support nested schema for the topic.
  • s

    Sandeep Nayak

    11/13/2019, 5:22 AM
    It would entail each table consumer would have to read each message and discard appropriately…would slow down ingestion
  • s

    Sandeep Nayak

    11/13/2019, 5:23 AM
    Also not a great idea if some tables expect higher volumes
  • m

    Mayank

    11/13/2019, 5:23 AM
    Unless these topics are quite overlapping, it will be an overhead
  • m

    Mayank

    11/13/2019, 5:23 AM
    *schema
  • s

    Sandeep Nayak

    11/13/2019, 5:25 AM
    On the
    tenants
    section, is that to be thought of in the context of tenancy as in data belonging to multiple different tenants in the same table? How do I think of this tenant section?
  • s

    Sandeep Nayak

    11/13/2019, 5:30 AM
    It appears I cannot have multiple
    outgoingGranularitySpec
    say I push timeseries data and want rollups say hypotetically 15min, 30min, 1 hr?
  • m

    Mayank

    11/13/2019, 5:32 AM
    Yeah, we have discussed that in the past, but not supported yet
  • k

    Kishore G

    11/13/2019, 5:32 AM
    Hmm
  • k

    Kishore G

    11/13/2019, 5:33 AM
    @User It is supported rt?
  • m

    Mayank

    11/13/2019, 5:33 AM
    Multiple time granularities?
  • m

    Mayank

    11/13/2019, 5:33 AM
    May be I am misreading the question?
  • s

    Sandeep Nayak

    11/13/2019, 5:34 AM
    Multiple rollup intervals
  • k

    Kishore G

    11/13/2019, 5:34 AM
    @User added that feature to have multiple datetimefieldspec
  • m

    Mayank

    11/13/2019, 5:35 AM
    Hmm, but do we have query processing that can figure out which rollup to use?
  • k

    Kishore G

    11/13/2019, 5:40 AM
    One can use startree rt
  • k

    Kishore G

    11/13/2019, 5:43 AM
    You can have time-15m, time-30, time-60 columns
  • m

    Mayank

    11/13/2019, 5:44 AM
    Yes, that works. I thought what @User was asking was more on what @User was working on
  • m

    Mayank

    11/13/2019, 5:44 AM
    the auto-rollup
  • k

    Kishore G

    11/13/2019, 5:45 AM
    No. Thats a bit advanced.
  • m

    Mayank

    11/13/2019, 5:45 AM
    but instead of auto, there's multiple outgoing granularities
  • m

    Mayank

    11/13/2019, 5:45 AM
    ok
  • s

    Sandeep Nayak

    11/13/2019, 5:46 AM
    @User mind explaining what you mean by “instead of auto, there’s multiple granularities”? How are they different?
  • k

    Kishore G

    11/13/2019, 5:47 AM
    @User Mayank is talking about logical time column vs physical
  • k

    Kishore G

    11/13/2019, 5:48 AM
    One can think that logically there is one time column
1...949596...160Latest