[ 
https://issues.apache.org/jira/browse/METRON-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Foley updated METRON-880:
------------------------------
    Description: 
Step 4 in design document.  Make clean interface with Profile usage.

While the Time Window Selector DSL is sort of stand-alone within Stellar, it is 
a powerful tool for addressing the kinds of queries against TSDB that Metron 
wants to do.  We should include it in Stellar and extract it.

Most of the functionality is currently in metron.profiler.client.window (path: 
metron-analytics/metron-profiler-client).  It is currently tightly integrated 
with the profiler, which has an idiosyncratic way of expressing its sampling 
timestamps (as HBase rowkeys).

I think there is already an intermediate form generated during processing of 
the DSL, as an array of time intervals, which can then be efficiently turned 
into the list of HBase rowkeys needed by the Profiler, but is not directly 
dependent on Profiler usages.  I propose this intermediate form as the API to 
the Time Window Selector DSL in an extracted Stellar.  The package would be 
metron.stellar.timewindow.

  was:Step 4 in design document.  Make clean interface with Profile usage.


> extract Time Window Selector DSL as part of metron-stellar
> ----------------------------------------------------------
>
>                 Key: METRON-880
>                 URL: https://issues.apache.org/jira/browse/METRON-880
>             Project: Metron
>          Issue Type: Sub-task
>            Reporter: Matt Foley
>
> Step 4 in design document.  Make clean interface with Profile usage.
> While the Time Window Selector DSL is sort of stand-alone within Stellar, it 
> is a powerful tool for addressing the kinds of queries against TSDB that 
> Metron wants to do.  We should include it in Stellar and extract it.
> Most of the functionality is currently in metron.profiler.client.window 
> (path: metron-analytics/metron-profiler-client).  It is currently tightly 
> integrated with the profiler, which has an idiosyncratic way of expressing 
> its sampling timestamps (as HBase rowkeys).
> I think there is already an intermediate form generated during processing of 
> the DSL, as an array of time intervals, which can then be efficiently turned 
> into the list of HBase rowkeys needed by the Profiler, but is not directly 
> dependent on Profiler usages.  I propose this intermediate form as the API to 
> the Time Window Selector DSL in an extracted Stellar.  The package would be 
> metron.stellar.timewindow.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to