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

ASF GitHub Bot commented on CLOUDSTACK-9298:
--------------------------------------------

Github user rafaelweingartner commented on the pull request:

    https://github.com/apache/cloudstack/pull/1425#issuecomment-195305570
  
    Now the error changed.
    It is in another table and probably is not related to your work.
    Now the problem is with "user_vm_view"
    Could you track who added that to the script?
    
    On Fri, Mar 11, 2016 at 7:01 AM, Nicolas Vazquez <[email protected]>
    wrote:
    
    > Thanks @rafaelweingartner <https://github.com/rafaelweingartner>
    >
    > I removed those lines but still not working:
    >
    > [ERROR] Failed to execute goal
    > org.codehaus.mojo:exec-maven-plugin:1.2.1:java (create-schema) on project
    > cloud-developer: An exception occured while executing the Java class. 
null:
    > InvocationTargetException: Unable to upgrade the database: Unable to
    > execute upgrade script:
    > 
/home/travis/build/apache/cloudstack/developer/target/db/db/schema-481to490.sql:
    > Table 'user_vm_view' already exists -> [Help 1]
    >
    > —
    > Reply to this email directly or view it on GitHub
    > <https://github.com/apache/cloudstack/pull/1425#issuecomment-195303532>.
    >
    
    
    
    -- 
    Rafael Weingärtner



> Improve performance of resource retrieval that have tags associated and 
> target volumes, VMs and templates
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9298
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9298
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: API
>    Affects Versions: 4.9.0
>            Reporter: Nicolas Vazquez
>             Fix For: 4.9.0
>
>
> h2. Description of the problem
> When retrieving a large number of resources which have tags associated with, 
> retrieval methods took too long. Our goal is to improve performance of this 
> methods avoiding query the database for each tag, managing that information 
> in memory.
> API methods to improve: {{listTemplates}}, {{listVolumes}}, 
> {{listVirtualMachines}}
> To achive it, it's necessary to include new columns in {{template_view}}, 
> {{volume_view}} and {{user_vm_view}}:
> * tag_account_name
> * tag_domain_name
> * tag_domain_uuid



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

Reply via email to