Opened 5 years ago
Closed 5 years ago
#2027 closed defect (fixed)
petascope: read coverage object from database for updating without cache
| Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
|---|---|---|---|
| Priority: | major | Milestone: | 9.8 |
| Component: | petascope | Version: | 9.7 |
| Keywords: | Cc: | Dimitar Misev, Vlad Merticariu | |
| Complexity: | Medium |
Description (last modified by )
Currently, when petascope reads coverage object from database, it caches this object to be reused later (e.g: for DescribeCoverage). However, this makes a problem with updating coverage, when an error happens, coverage object also updated and returns an incorrect result (e.g: geo axis increases bounds) as the data cannot update yet.
Change History (3)
comment:1 by , 5 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | petascope_investigate about @Transactional in Hibernate with auto flush → petascope_read coverage object from database for updating without cache |
comment:2 by , 5 years ago
| Summary: | petascope_read coverage object from database for updating without cache → petascope: read coverage object from database for updating without cache |
|---|
comment:3 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
It sounds like a transactional issue: on error the coverage object should not be updated.