[
https://issues.jboss.org/browse/TEIID-1861?page=com.atlassian.jira.plugin...
]
Johnathon Lee commented on TEIID-1861:
--------------------------------------
This behavior is still confusing to me. I modified my unit test[1] and return similar
results[2]. I understand that your saying the capabilities need to reflect literal
projection... but that's where the confusion comes in. It is handling the literal
projection of the first two entries ( x1, x2 ). It returns null on the third. The third
being an arbitrary stopping point, since I can achieve similar results w/X amount of
literals.
[1]
@Test public void testTupleBufferInTestFramework(){
String sql = "SELECT 'x1', 'x2', 'x3' FROM
pm1.g1";
// Create expected results - would expect these to be:
List[] expected = new List[] {
Arrays.asList("x1", "x2", "x3")
};
// Construct data manager with data
HardcodedDataManager dataManager = new HardcodedDataManager();
dataManager.setMustRegisterCommands(false);
Command command = helpParse(sql);
ProcessorPlan plan = helpGetPlan(command, RealMetadataFactory.example1Cached(),
TestOptimizer.getGenericFinder(false));
// Run query
helpProcess(plan, dataManager, expected);
}
[2]
Results:
['x1', 'x2', 'x3']
0: [x1, x2, null]
TupleBuffer used in TestProcessor is being treated as a 1 based
array.
----------------------------------------------------------------------
Key: TEIID-1861
URL:
https://issues.jboss.org/browse/TEIID-1861
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.6.1
Reporter: Johnathon Lee
Assignee: Steven Hawkins
The test framework is returning nulls for literals specified in a query.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira