Ticket #201 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

Total number of assets is not identical on different calls

Reported by: Michiel.Schok Owned by: MC-arjen
Priority: major Milestone: MediaMosa 1.7
Component: Core Version: 1.7.2
Keywords: Cc:
MoSCoW: Estimated time after impact analysis:
Related to project: none Tested:
Accepted: yes Estimated Hours:

Description

Since 1.7 release, I observe on the VP-core staging platform the following behaviour. Main focus of this ticket is the total count of assets found.

calltotal assets
[GET] asset?limit=10199
[GET] asset?limit=10&user_id=nibg-admin32609
[GET] asset?limit=10&user_id=SURFNET.michiel199

We expect the total to be the same, because it doesn't matter which user is logged on to see the master/slave records.

On Core - production, the counts are almost right, I cannot imagine what the single asset is that does not appear... (but that's another discussion)

call to productiontotal assets
[GET] asset?limit=1061632
[GET] asset?limit=10&user_id=nibg-admin61631
[GET] asset?limit=10&user_id=SURFNET.michiel61632

Responses for staging environment are given below.

<?xml version="1.0"?>
<response>
  <header>
    <item_count>10</item_count>
    <item_count_total>199</item_count_total>
    <item_offset>0</item_offset>
    <request_process_time>0.0404</request_process_time>
    <request_query_count>21</request_query_count>
    <request_result>success</request_result>
    <request_result_description></request_result_description>
    <request_result_id>601</request_result_id>
    <request_uri>[GET] asset?limit=10</request_uri>
    <vpx_version>1.7.0.1</vpx_version>
  </header>
  <items>
<?xml version="1.0"?>
<response>
  <header>
    <item_count>10</item_count>
    <item_count_total>32609</item_count_total>
    <item_offset>0</item_offset>
    <request_process_time>0.9418</request_process_time>
    <request_query_count>24</request_query_count>
    <request_result>success</request_result>
    <request_result_description></request_result_description>
    <request_result_id>601</request_result_id>
    <request_uri>[GET] asset?limit=10&amp;user_id=nibg-admin</request_uri>
    <vpx_version>1.7.0.1</vpx_version>
  </header>
  <items>
<?xml version="1.0"?>
<response>
  <header>
    <item_count>10</item_count>
    <item_count_total>199</item_count_total>
    <item_offset>0</item_offset>
    <request_process_time>0.2898</request_process_time>
    <request_query_count>34</request_query_count>
    <request_result>success</request_result>
    <request_result_description></request_result_description>
    <request_result_id>601</request_result_id>
    <request_uri>[GET] asset?limit=10&amp;user_id=SURFNET.michiel</request_uri>
    <vpx_version>1.7.0.1</vpx_version>
  </header>
  <items>

Change History

Changed 2 years ago by forgacs

  • owner set to MC-arjen
  • status changed from new to assigned

Changed 2 years ago by forgacs

Michiel, Would you write me what was your VP-X connector settings?
(User name, URL)

Changed 2 years ago by MC-arjen

  • status changed from assigned to closed
  • version set to 1.7.2
  • resolution set to fixed

unfortunately we cannot reproduce this in 1.7.1/1.7.2...

[GET] asset?limit=10&amp;user_id=SURFNET.Michiel32680
[GET] asset?limit=10&user_id=nibg-admin32680
[GET] asset?limit=1032680

Perhaps this had something todo with the application copy which had not run completely?

Changed 2 years ago by Frans

  • accepted changed from no to yes

Problem solved...

Note: See TracTickets for help on using tickets.