Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Description

None

Attachments

1
  • 29 Oct 2015, 03:14 PM

depends on

Activity

Show:

Steve Ebersole October 8, 2021 at 7:10 PM

I believe this is already done on 6.0. Please give it a try there and let us know if you still see issues

Steve Ebersole May 10, 2016 at 2:02 PM

Lets look at this as part of the SQM work

Steve Ebersole October 29, 2015 at 4:05 PM

Steve Ebersole October 29, 2015 at 4:00 PM

I played around really quickly with using the source HQL as the cache key instead. Good and bad. The CacheKey becomes very sensitive to unimportant source variations. For example there were failures in the testsuite initially where we were testing the caching of the following queries:

  • from Animal a where a.age > ?

  • select a from Animal a where a.age > ?

So functionally they are the same query, but different in the source representation - here we get 2 different CacheKeys and thus a cache miss for the second execution.

I'll create a branch in my fork for everyone to be able to see and discuss in triage.

Christian Beikov October 29, 2015 at 3:14 PM

Indeed turned out to be problematic.

Something went wrong on our end

If this keeps happening, share this information with your admin, who should contact support.

Hash K7MH2U Trace 23d88120164a450182ea0c6ca18d8509

Details

Assignee

Unassigned

Reporter

Marcus Winkler

Components

Affects versions

Priority

Major

Flag notifications