[
https://issues.jboss.org/browse/TEIID-4471?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-4471.
-----------------------------------
Resolution: Done
You can look into adapting the unit test to reproduce. The
TestTempTables.testDeleteRemovingPage
https://github.com/teiid/teiid/blob/1b1963b5c7bac258a2b8b749d71b72413f695...
performs the same deletion scenario (helpTestDelete) three times with various settings
1. Test defaults (BufferManagerFactory), 256 batch size, max object storage size of 1 MB,
and memory buffer space of 2 MB.
2. Small memory (max reserve/processing of ~1000KB) and batch size (10 rows)
3. Mixed memory (max reserve/processing of ~1000KB) and batch size (250 rows)
Assertion error with temp table delete
--------------------------------------
Key: TEIID-4471
URL:
https://issues.jboss.org/browse/TEIID-4471
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 9.1, 8.13.7, 9.0.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12.8.6_3, 9.0.5, 8.13.7, 9.1
Related to TEIID-4405 there are circumstances where a temp table deletion results in an
assertion error of "delete failed". A possible scenario (that is dependent upon
a number of factors, including batch sizes and garbage collection) requires the values
stored by the tuple browser to get out of sync with what is stored by the page such that a
delete is attempted twice.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)