bugs when some configs is not default value
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Stado |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
Hi,
There is problem with some configs if they are not set to default value.
1). xdb.identifier.
The default value is "\"", and in SqlExpression.java rebuildExpressi
aSqlExpression.
This will cause problem if we set the config with a new value (e.g. "\`") other than "\"", for example, when executing the SQL
select name,count(*) from info group by name;
The query plan contains a query string like:
select ```in````na```, count(*) ....
This is incorrect.
Update aSqlExpression.
aSqlExpression.
can fix this bug.
2). xdb.use_
The default value is "true".
If we set it to false. When executing a SQL like
insert into info2 select * from info;
An exception is got:
Node 1 has aborted execution, cause is: java.lang.
The cause is in ProducerSender.
if (aStepDetail.
...
From the execution step, the targetSchema is null, so this statement will cause exception.
Adding check with (aStepDetail.
1) I do not see aSqlExpression. exprString. startsWith( "\"") in the SqlExpression.java rebuildExpressi on(...) function, probably you are working with modified code. Anyway, it looks like proper fix is aSqlExpression. exprString. startsWith( Props.XDB_ IDENTIFIER_ QUOTE_START) ;
2) Fix for this case is committed.