Thank you for the clarification.
On 6 Oct 2017 05:08, "Jacky Li" wrote:
> I mean, either spark.sql.warehouse.dir is set by user,
> the carbon core should not be aware of database and related
> path construction logic should be kept in spark or
> spark-integration module
n case of spark the where to write the table content is decided in two ways.
1. If a table is created under a database for which loaction attribute is
not configured by the end user,
then the content of table will be written in the
"spark.sql.warehouse.dir".
For example: if
Hi,
Instead of using SET command to use for segments why don't you use QUERY
HINT . Using query hint we can mention the segments inside the query itself
as a hint.
For example SELECT /*+SEGMENTS(1,3,5) */ from t1.
By using the above custom hint we can query from selected segments only,
This
@Jacky please find the reply of your doubts as follow :
*1.If user uses following command in two different beeline session,
will there be problem due to multithreading? SET
carbon.input.segments.default.*
*carbontable=1,3,5; select * from carbontable; SET