[GitHub] [carbondata] ajantha-bhat commented on issue #3243: [CARBONDATA-3401] fix the java sdk create wrong carbondata filename

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] [carbondata] ajantha-bhat commented on issue #3243: [CARBONDATA-3401] fix the java sdk create wrong carbondata filename

GitBox
ajantha-bhat commented on issue #3243: [CARBONDATA-3401] fix the java sdk create wrong carbondata filename
URL: https://github.com/apache/carbondata/pull/3243#issuecomment-544862985
 
 
   @lamber-ken : In SDK writer, both taskNo and timestamp are configurable. If user wants milli, user can configure the value.
   
   Also SDK uses nano Second time so that in concurrency the chances that it will be unique than milli seconds.
   
   You might saw that name will have `taskNo, batch_prefix, batchNo, bucketNumber, segmentNo, factUpdateTimestamp`. But in most of the cases `batchNo, bucketNumber` will be zero and segmentNo will be null for SDK.
   
   so only differentiating parameters is task number and timestamp. In case of multi-thread SDK writing. task number also same. same task will write multiple files concurrently. That time to avoid same name we use nanoSeconds.
   
   In carbon session this problem will not come as segment will not be null.
   
   So I guess, that current design solves the problem. If we change to milli second, we get issues

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


With regards,
Apache Git Services