[
https://issues.apache.org/jira/browse/AMBARI-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507342#comment-13507342
]
Tom Beerbower commented on AMBARI-1043:
---------------------------------------
The use of non-existent properties or properties that are not supported for a
given resource type will now result in an UnsupportedPropertyException. This
applies to any CRUD operation on the cluster controller.
Updates and deletes that use a predicate that contains supported properties
that can not be understood by the resource provider (obtained from a property
provider) will now be completed in two phases :
1) Use the given predicate to do a get resources, requesting the primary key
fields for that resource type.
2) Complete the update or delete operation, using the resources returned in
step 1 to create a new predicate based on the primary key fields.
> Updates with queries that contain non primary key fields may update resources
> that don't satisfy the query
> ----------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-1043
> URL: https://issues.apache.org/jira/browse/AMBARI-1043
> Project: Ambari
> Issue Type: Sub-task
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Attachments: AMBARI-1043.patch
>
>
> Resource updates via the REST API which have queries that contain non primary
> key properties may result in updates to resources which don't fully satisfy
> the query.
> Also, updates that have queries which contain non-existent properties don't
> flag the invalid property and simply ignore that predicate.
--
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
