Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
The SimpleDateFormat is used to convert string and timestamp. But
SimpleDateFormat doesn't support nanoseconds and microsecond, which is is incompatiable with DB&Spark&Hive. To support nanoseconds and microsecond, we shall change SimpleDateFormat to DateTimeFormatter. Shall we involve this work? -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
+1, please consider compatable for history data
-- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
+ 1,
as SimpleDateFormat doesn't support nanoseconds and microsecond. Thanks, Ajantha On Tue, Jul 14, 2020 at 5:03 PM xubo245 <[hidden email]> wrote: > +1, please consider compatable for history data > > > > -- > Sent from: > http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ > |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
In reply to this post by haomarch
+1
----- My English name is Sunday -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
My English name is Sunday
|
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Hi,
I think it is bigger than just changing to DateTimeFormatter. As of now, carbon uses only 64 bit to store timestamp so it can accommodate till milliseconds. In order to support till nanoseconds, we need to use 96 bits. If you check spark-parquet it uses 96 bits to store timestamp. It would be good if we also go in that direction to support till nanosecond level. Thank you. Regards, Ravindra. On Wed, 15 Jul 2020 at 14:50, Zhangshunyu <[hidden email]> wrote: > +1 > > > > ----- > My English name is Sunday > -- > Sent from: > http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ > -- Thanks & Regards, Ravi |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Hi,
I agree with Ravi, first we need to come up with solution how to store till nano/mico second in carbon. Then changing the formatter will be useful for us. Regards Kumar Vishal On Wed, 15 Jul 2020 at 6:18 PM, Ravindra Pesala <[hidden email]> wrote: > Hi, > > I think it is bigger than just changing to DateTimeFormatter. As of now, > carbon uses only 64 bit to store timestamp so it can accommodate till > milliseconds. In order to support till nanoseconds, we need to use 96 > bits. If you check spark-parquet it uses 96 bits to store timestamp. It > would be good if we also go in that direction to support till nanosecond > level. Thank you. > > Regards, > Ravindra. > > On Wed, 15 Jul 2020 at 14:50, Zhangshunyu <[hidden email]> wrote: > > > +1 > > > > > > > > ----- > > My English name is Sunday > > -- > > Sent from: > > http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ > > > > > -- > Thanks & Regards, > Ravi > ... [show rest of quote]
kumar vishal
|
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
In reply to this post by ravipesala
agree with Ravi
----- Best Regards David Cai -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
Best Regards
David Cai |
Free forum by Nabble | Edit this page |