]
Paul Richardson commented on TEIIDDES-2414:
-------------------------------------------
[~shawkins]
I think at this stage spanning blocks would be unnecessary. Allowing management of the
block size should be sufficient. My thoughts ....
The bug has emerged from the transformation SELECT query in the view model (generated from
test.csv) being about 9K in size. You are probably more aware than I but the algorithm
works by adding a 'word entry' to an index block. If that word entry fails to fit
in the block then that block is written and a new block created to occupy the word entry.
Since the SELECT query is 9K it fails to fit in an empty block so is lost from the index
completely. Increasing the size of the index block allows for such an entry to be
accomodated. The downside is more word entries per block but I presume that is the price
to be paid for accommodating such a large query.
In this usecase, would a vdb metadata property be more useful over a system property? My
thought is that the vdb is then in control of how its indexes were created and can tell
teiid how they should be read on a pre-vdb basis rather than stipulating the property for
all vdbs in the running teiid.
Large transformation SQL is not exported to INDEX file.
-------------------------------------------------------
Key: TEIIDDES-2414
URL:
https://issues.jboss.org/browse/TEIIDDES-2414
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.3.4
Reporter: Hisanobu Okuda
Assignee: Paul Richardson
Fix For: 9.2.1
Attachments: reosurce-problem-marker.png, test.csv
A large transformation SQL of a view model is not exported to INDEX file.
I have a large transformation SQL > 8192 bytes in my view model. TDesigner fails to
convert the xmi to XXXXXXXXXX.INDEX file. There is no transformation SQL in the INDEX
file, therefore, deploying my vdb fails and the vdb is inactivated. When you deploy the
vdb, you can see the following message in a log file:-
{code}
17:16:11,632 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2) TEIID31079 View
ViewModel.new_table is not defined by a query expression.
17:16:11,636 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40073 The metadata
for the VDB test.1 is loaded, however it is not valid. Check models for errors. Correct
the metadata and re-deploy.
17:16:11,637 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40003 VDB test.1 is
set to FAILED
{code}