[ANALYTICS-314] Wrong cache value with Periscope and ContentTag data supplier Created: 03/Mar/21  Updated: 12/Mar/21  Resolved: 10/Mar/21

Status: Closed
Project: Analytics
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2

Type: Bug Priority: Neutral
Reporter: Yen Lac Tue Assignee: Oanh Thai Hoang
Resolution: Fixed Votes: 0
Labels: VN-Testing
Remaining Estimate: 0d
Time Spent: 2d 6.75h
Original Estimate: Not Specified

Attachments: Text File duplicate_hashcode_with_different_params.txt     PNG File wrong_column_content_tags.png    
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: UI/UX Dash improvements
Sprint: Add-Ons 59
Story Points: 5

 Description   

Steps to reproduce

  1.  Access "demo" dashboard
  2.  Click on filter icon to expand filter bar
  3. Please refer attach file and follow step by step input value for "Limit of frequent search" and "Number of content tags" to reproduce it

You can see that with filter value {limitTopSearch=3, numberOfTags=6} and {limitTopSearch=4, numberOfTags=3}, the datasuppliers have the same hashcode is -2029840277

.. Logs, screenshots, gifs...

Expected results

Charts display correctly with filter value.. .

Actual results

Charts display the wrong number of filtering value

Workaround

Development notes


Generated at Sun Feb 11 23:17:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.