You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "John Speidel (JIRA)" <ji...@apache.org> on 2012/10/15 20:34:03 UTC

[jira] [Created] (AMBARI-862) API query against /clusters doesn't return any data

John Speidel created AMBARI-862:
-----------------------------------

             Summary: API query against /clusters doesn't return any data
                 Key: AMBARI-862
                 URL: https://issues.apache.org/jira/browse/AMBARI-862
             Project: Ambari
          Issue Type: Bug
            Reporter: John Speidel
            Assignee: John Speidel


Queries against /clusters don't return any data even if they should.
This is a result of how the query predicate is built.  Because clusters doesn't have a parent, the internal query is null.  When the user predicate is combined with the internal predicate, we weren't checking to see if the internal predicate is null.  This resulted in an AND predicate with the user predicate and a null predicate.

This bug only affects /clusters queries as it is the only top level resource at this time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (AMBARI-862) API query against /clusters doesn't return any data

Posted by "John Speidel (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Speidel updated AMBARI-862:
--------------------------------

    Description: 
Queries against /clusters don't return any data when a user predicate is provided, even if they should.
This is a result of how the query predicate is built.  Because clusters doesn't have a parent, the internal query is null.  When the user predicate is combined with the internal predicate, we weren't checking to see if the internal predicate is null.  This resulted in an AND predicate with the user predicate and a null predicate.

This bug only affects /clusters queries as it is the only top level resource at this time.

  was:
Queries against /clusters don't return any data even if they should.
This is a result of how the query predicate is built.  Because clusters doesn't have a parent, the internal query is null.  When the user predicate is combined with the internal predicate, we weren't checking to see if the internal predicate is null.  This resulted in an AND predicate with the user predicate and a null predicate.

This bug only affects /clusters queries as it is the only top level resource at this time.

    
> API query against /clusters doesn't return any data
> ---------------------------------------------------
>
>                 Key: AMBARI-862
>                 URL: https://issues.apache.org/jira/browse/AMBARI-862
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: John Speidel
>            Assignee: John Speidel
>         Attachments: AMBARI-862.patch
>
>
> Queries against /clusters don't return any data when a user predicate is provided, even if they should.
> This is a result of how the query predicate is built.  Because clusters doesn't have a parent, the internal query is null.  When the user predicate is combined with the internal predicate, we weren't checking to see if the internal predicate is null.  This resulted in an AND predicate with the user predicate and a null predicate.
> This bug only affects /clusters queries as it is the only top level resource at this time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (AMBARI-862) API query against /clusters doesn't return any data

Posted by "John Speidel (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Speidel updated AMBARI-862:
--------------------------------

    Attachment: AMBARI-862.patch
    
> API query against /clusters doesn't return any data
> ---------------------------------------------------
>
>                 Key: AMBARI-862
>                 URL: https://issues.apache.org/jira/browse/AMBARI-862
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: John Speidel
>            Assignee: John Speidel
>         Attachments: AMBARI-862.patch
>
>
> Queries against /clusters don't return any data even if they should.
> This is a result of how the query predicate is built.  Because clusters doesn't have a parent, the internal query is null.  When the user predicate is combined with the internal predicate, we weren't checking to see if the internal predicate is null.  This resulted in an AND predicate with the user predicate and a null predicate.
> This bug only affects /clusters queries as it is the only top level resource at this time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (AMBARI-862) API query against /clusters doesn't return any data

Posted by "Yusaku Sako (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yusaku Sako updated AMBARI-862:
-------------------------------

    Issue Type: Sub-task  (was: Bug)
        Parent: AMBARI-666
    
> API query against /clusters doesn't return any data
> ---------------------------------------------------
>
>                 Key: AMBARI-862
>                 URL: https://issues.apache.org/jira/browse/AMBARI-862
>             Project: Ambari
>          Issue Type: Sub-task
>            Reporter: John Speidel
>            Assignee: John Speidel
>         Attachments: AMBARI-862.patch
>
>
> Queries against /clusters don't return any data when a user predicate is provided, even if they should.
> This is a result of how the query predicate is built.  Because clusters doesn't have a parent, the internal query is null.  When the user predicate is combined with the internal predicate, we weren't checking to see if the internal predicate is null.  This resulted in an AND predicate with the user predicate and a null predicate.
> This bug only affects /clusters queries as it is the only top level resource at this time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira