[GitHub] metron pull request #965: METRON-590 Enable Use of Event Time in Profiler

Github user nickwallen commented on a diff in the pull request: https://github.com/apache/metron/pull/965#discussion_r175586013 --- Diff: metron-analytics/metron-profiler/README.md --- @@ -328,6 +328,62 @@ Continuing the previous running example, at this point, you have seen how

[jira] [Commented] (METRON-590) Enable Use of Event Time in Profiler

[ https://issues.apache.org/jira/browse/METRON-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405448#comment-16405448 ] ASF GitHub Bot commented on METRON-590: --- Github user nickwallen commented on a diff in the pull

[jira] [Commented] (METRON-1491) The indexing topology restart logic is wrong

[ https://issues.apache.org/jira/browse/METRON-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405297#comment-16405297 ] ASF GitHub Bot commented on METRON-1491: Github user ottobackwards commented on the issue:

[jira] [Commented] (METRON-590) Enable Use of Event Time in Profiler

[ https://issues.apache.org/jira/browse/METRON-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405296#comment-16405296 ] ASF GitHub Bot commented on METRON-590: --- Github user cestella commented on a diff in the pull

[GitHub] metron issue #964: METRON-1491: The indexing topology restart logic is wrong

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/964 +1 by inspection ---

[GitHub] metron pull request #965: METRON-590 Enable Use of Event Time in Profiler

Github user cestella commented on a diff in the pull request: https://github.com/apache/metron/pull/965#discussion_r175553846 --- Diff: metron-analytics/metron-profiler/README.md --- @@ -328,6 +328,62 @@ Continuing the previous running example, at this point, you have seen how

[jira] [Commented] (METRON-1491) The indexing topology restart logic is wrong

[ https://issues.apache.org/jira/browse/METRON-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405290#comment-16405290 ] ASF GitHub Bot commented on METRON-1491: Github user cestella commented on the issue:

[GitHub] metron issue #964: METRON-1491: The indexing topology restart logic is wrong

Github user cestella commented on the issue: https://github.com/apache/metron/pull/964 Ok, I ran this up in full-dev and it functions as advertised. Killing one of the indexing topologies and then starting, does not try to start the other topology. ---

[jira] [Commented] (METRON-1498) Null Is Not Allowed for 'foreach' and 'onlyif' Profiler Expressions

[ https://issues.apache.org/jira/browse/METRON-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405137#comment-16405137 ] Nick Allen commented on METRON-1498: Not a bug.  Ignore > Null Is Not Allowed for 'foreach' and

[jira] [Updated] (METRON-1498) Null Is Not Allowed for 'foreach' and 'onlyif' Profiler Expressions

[ https://issues.apache.org/jira/browse/METRON-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Allen updated METRON-1498: --- Affects Version/s: (was: 0.4.2) > Null Is Not Allowed for 'foreach' and 'onlyif' Profiler

[jira] [Updated] (METRON-1498) Null Is Not Allowed for 'foreach' and 'onlyif' Profiler Expressions

[ https://issues.apache.org/jira/browse/METRON-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Allen updated METRON-1498: --- Priority: Minor (was: Major) > Null Is Not Allowed for 'foreach' and 'onlyif' Profiler Expressions

[jira] [Updated] (METRON-1498) Null Is Not Allowed for 'foreach' and 'onlyif' Profiler Expressions

[ https://issues.apache.org/jira/browse/METRON-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Allen updated METRON-1498: --- Fix Version/s: (was: Next + 1) > Null Is Not Allowed for 'foreach' and 'onlyif' Profiler

[jira] [Created] (METRON-1498) Null Is Not Allowed for 'foreach' and 'onlyif' Profiler Expressions

Nick Allen created METRON-1498: -- Summary: Null Is Not Allowed for 'foreach' and 'onlyif' Profiler Expressions Key: METRON-1498 URL: https://issues.apache.org/jira/browse/METRON-1498 Project: Metron

[jira] [Commented] (METRON-1465) X-pack support for Elasticsearch

[ https://issues.apache.org/jira/browse/METRON-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404997#comment-16404997 ] ASF GitHub Bot commented on METRON-1465: Github user wardbekker commented on the issue:

[GitHub] metron issue #946: METRON-1465:Support for Elasticsearch X-pack

Github user wardbekker commented on the issue: https://github.com/apache/metron/pull/946 @mmiklavc great stuff. merged! ---

[jira] [Commented] (METRON-1465) X-pack support for Elasticsearch

[ https://issues.apache.org/jira/browse/METRON-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404981#comment-16404981 ] ASF GitHub Bot commented on METRON-1465: Github user mmiklavc commented on the issue:

[GitHub] metron issue #946: METRON-1465:Support for Elasticsearch X-pack

Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/946 @wardbekker I have a PR against your PR. Can you please review when you have a moment? ---

[jira] [Commented] (METRON-1497) Rest endpoint '/api/v1/search/search' needs to handle null when elastic search response return null for getAggregations

[ https://issues.apache.org/jira/browse/METRON-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404763#comment-16404763 ] ASF GitHub Bot commented on METRON-1497: GitHub user MohanDV opened a pull request:

[GitHub] metron pull request #968: METRON-1497: Rest endpoint '/api/v1/search/search'...

GitHub user MohanDV opened a pull request: https://github.com/apache/metron/pull/968 METRON-1497: Rest endpoint '/api/v1/search/search' needs to handle null when elastic search response return null for getAggregations ## Contributor Comments Handle null value when elastic

[jira] [Updated] (METRON-1497) Rest endpoint '/api/v1/search/search' needs to handle null when elastic search response return null for getAggregations

[ https://issues.apache.org/jira/browse/METRON-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohan updated METRON-1497: -- Summary: Rest endpoint '/api/v1/search/search' needs to handle null when elastic search response return null

[jira] [Created] (METRON-1497) /api/v1/search/search needs to handle null when elastic search response return null for getAggregations

Mohan created METRON-1497: - Summary: /api/v1/search/search needs to handle null when elastic search response return null for getAggregations Key: METRON-1497 URL: https://issues.apache.org/jira/browse/METRON-1497

[jira] [Commented] (METRON-1347) Indexing Topology should fail tuples without a source.type

[ https://issues.apache.org/jira/browse/METRON-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404684#comment-16404684 ] ASF GitHub Bot commented on METRON-1347: Github user ottobackwards commented on the issue:

[GitHub] metron issue #863: METRON-1347: Indexing Topology should fail tuples without...

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/863 What I think would be better would be to have a readme about the required fields and refer to that document from these other documents ---

[GitHub] metron issue #863: METRON-1347: Indexing Topology should fail tuples without...

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/863 The parser topology PRODUCES the original_string. By that very action, and it's requirement, it can only be used and required by downstream usages either from rest ( post indexing ) or during

[jira] [Updated] (METRON-1496) ChainLink Parser to reuse parser code at parserConfig level

[ https://issues.apache.org/jira/browse/METRON-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas van de Lustgraaf updated METRON-1496: - Description: During the development of some custom parsers we wrote a couple of

[jira] [Updated] (METRON-1496) ChainLink Parser to reuse parser code at parserConfig level

[ https://issues.apache.org/jira/browse/METRON-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas van de Lustgraaf updated METRON-1496: - Description: During the development of some custom parsers we wrote a couple of

[jira] [Created] (METRON-1496) ChainLink Parse to reuse parser code at parserConfig level

Bas van de Lustgraaf created METRON-1496: Summary: ChainLink Parse to reuse parser code at parserConfig level Key: METRON-1496 URL: https://issues.apache.org/jira/browse/METRON-1496 Project:

[jira] [Updated] (METRON-1496) ChainLink Parser to reuse parser code at parserConfig level

[ https://issues.apache.org/jira/browse/METRON-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bas van de Lustgraaf updated METRON-1496: - Summary: ChainLink Parser to reuse parser code at parserConfig level (was: