[
https://issues.apache.org/jira/browse/HIVE-18075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281381#comment-16281381
]
Harish Jaiprakash commented on HIVE-18075:
------------------------------------------
For 1: Cannot drop pool/RP with mapping.
For pool with mapping:
It does show a message "Exception thrown flushing changes to datastore", when
trying to drop a pool which is has mappings. And there is a test case which
checks exactly this :-). Sorry, about that I thought it was lil bit
in-efficient to query mappings. I'll see if there is an efficient way to see
check the exact constraint violation.
I'll check RP with mapping, the code seems to be removing all the mappings and
the test seems to be removing them too.
For 2: I get this message, and there is a test for it too. "Cannot drop default
pool of a resource plan".
For 3: I've a fix for duplicate resource plan name now. Will add a test case to
create plan with same name again and see the results.
> verify commands on a cluster
> ----------------------------
>
> Key: HIVE-18075
> URL: https://issues.apache.org/jira/browse/HIVE-18075
> Project: Hive
> Issue Type: Sub-task
> Reporter: Sergey Shelukhin
> Assignee: Harish Jaiprakash
>
> I was running the commands in the cluster, with potentially a slightly
> outdated version of the DB on mysql (yet, the DB was created with a script
> from master and I didn't hit any schema issues, so it's fairly recent);
> however, recent master code + the pools commands patch. I've hit the
> following issues.
> # Cannot drop pool or RP with a mapping (see also 3).
> # Cannot drop pool that is set as default (probably correct, but the error
> message is bad).
> # When I dropped an RP with a mapping, and then created it again with the
> same name, the pool creation in that RP would fail with an error that a
> unique query returned multiple results. In the DB, there were actually 2 RPs
> with the same name. Not sure how exactly that happened, there might have been
> intermediate states, but I didn't mess with mysql. I think the name
> uniqueness is either missing from some script or doesn't work.
> # -Setting RP default pool no longer works. I think I might have broken it
> with one of the rebases in that area, but it could also be something else (or
> like other things, it works in q tests but not on cluster for whatever
> reason-).
> # -Resource plan rename doesn't check the disable state. It probably should.
> Also need to see for other commands-.
> Need to figure out which are real issues and which aren't and fix.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
