[ 
https://issues.apache.org/jira/browse/METRON-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633307#comment-15633307
 ] 

ASF GitHub Bot commented on METRON-535:
---------------------------------------

GitHub user cestella reopened a pull request:

    https://github.com/apache/incubator-metron/pull/341

    METRON-535: Global Validations type still refers to MQL rather than Stellar

    The global validation processor that allows you to specify global 
validations via Stellar is still named "MQL" rather than "STELLAR". The 
documentation states otherwise. This is inconsistent and should have its name 
changed.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cestella/incubator-metron METRON-535

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-metron/pull/341.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #341
    
----
commit 0b396e8e030f57683b831858f42bbc4f0a3be41d
Author: cstella <[email protected]>
Date:   2016-11-03T14:15:04Z

    METRON-535: Global Validations type still refers to MQL rather than Stellar

----


> Global Validations type still refers to MQL rather than Stellar
> ---------------------------------------------------------------
>
>                 Key: METRON-535
>                 URL: https://issues.apache.org/jira/browse/METRON-535
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Casey Stella
>            Assignee: Casey Stella
>             Fix For: 0.2.2BETA
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The global validation processor that allows you to specify global validations 
> via Stellar is still named "MQL" rather than "STELLAR".  The documentation 
> states otherwise.  This is inconsistent and should have its name changed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to