Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone
This vote passes with 6 binding and 3 non-binding +1 votes. I will update the PR[1] from draft to "ready for review". Thanks for bearing with all the votes :) [1] https://github.com/apache/arrow/pull/10629 On Fri, Jul 2, 2021 at 1:40 AM Kazuaki Ishizaki wrote: > > +1 > > Kazuaki Ishizaki > > "Weston Pace" wrote on 2021/06/30 18:52:46: > > > From: "Weston Pace" > > To: dev@arrow.apache.org > > Date: 2021/06/30 18:53 > > Subject: [EXTERNAL] [VOTE] Arrow should state a convention for > > encoding instants as Timestamp with "UTC" as the time zone > > > > This vote is a result of previous discussion[1][2]. This vote is also > > a prerequisite for the PR in [5]. > > > > --- > > Some date & time libraries have three temporal concepts. For the sake > > of this document we will call them LocalDateTime, ZonedDateTime, and > > Instant. An Instant is a timestamp that has no meaningful reference > > time zone (e.g. events that did not occur on Earth or columns of > > timestamps spanning more than one time zone). For more extensive > > definitions and a discussion of their semantics and uses see [3]. > > Currently Arrow describes how to encode two of these three concepts > > into a Timestamp column and there is no guideline on how to store an > > Instant. > > > > > > This proposal states that Arrow should recommend that instants be > encoded > > into timestamp columns by setting the timezone string to "UTC". > > --- > > > > For sample arguments (currently grouped as "for changing schema.fbs" > > and "against changing schema.fbs") see [4]. For a detailed definition > > of the terms LocalDateTime, ZonedDateTime, and Instant and a > > discussion of their semantics see [3]. For a straw poll on > > possible ways to handle instants see [2]. > > > > This vote will be open for at least 72 hours. > > > > [ ] +1 Update schema.fbs to state the above convention > > [ ] +0 > > [ ] -1 Do not make any change > > > > [1] INVALID URI REMOVED > > > u=https-3A__lists.apache.org_thread.html_r8216e5de3efd2935e3907ad9bd20ce07e430952f84de69b36337e5eb-2540-253Cdev.arrow.apache.org-253E=DwIBaQ=jf_iaSHvJObTbx- > > siA1ZOg=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f- > > ZCGj9Pg=avV0JpLmaymMbxpZiYwNb9Yug7bj3PGiNYiJCM-x3kY=Ty-Oq- > > Gfuo2KRdogmjFFOLvji5yQ0LrrBZWWO7hDufs= > > [2] INVALID URI REMOVED > > > u=https-3A__lists.apache.org_thread.html_r1bdffc76537ae9c12c37396880087fee9c0eec9000bf6ed4c9850c44-2540-253Cdev.arrow.apache.org-253E=DwIBaQ=jf_iaSHvJObTbx- > > siA1ZOg=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f- > > ZCGj9Pg=avV0JpLmaymMbxpZiYwNb9Yug7bj3PGiNYiJCM- > > x3kY=NyxlTSPly7kAqwMiuXS7BH0lZkK3W0VmVSvvRF-ANa8= > > [3] INVALID URI REMOVED > > > u=https-3A__docs.google.com_document_d_1QDwX4ypfNvESc2ywcT1ygaf2Y1R8SmkpifMV7gpJdBI_edit-3Fusp-3Dsharing=DwIBaQ=jf_iaSHvJObTbx- > > siA1ZOg=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f- > > ZCGj9Pg=avV0JpLmaymMbxpZiYwNb9Yug7bj3PGiNYiJCM- > > x3kY=opFrDCQFvlSmY31hxs8MDKLcUe3muSTaNXosFCaPX5U= > > [4] INVALID URI REMOVED > > > u=https-3A__docs.google.com_document_d_1xEKRhs-2DGUSMwjMhgmQdnCNMXwZrA10226AcXRoP8g9E_edit-3Fusp-3Dsharing=DwIBaQ=jf_iaSHvJObTbx- > > siA1ZOg=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f- > > ZCGj9Pg=avV0JpLmaymMbxpZiYwNb9Yug7bj3PGiNYiJCM- > > x3kY=fIjWMI0tuH57ffsGzpOX85d5Dd7TN4tT_h0cj1elNbw= > > [5] INVALID URI REMOVED > > > u=https-3A__github.com_apache_arrow_pull_10629=DwIBaQ=jf_iaSHvJObTbx- > > siA1ZOg=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f- > > ZCGj9Pg=avV0JpLmaymMbxpZiYwNb9Yug7bj3PGiNYiJCM- > > x3kY=RQrwm8rHhpbx-6JbTZ4WMVpWGrUIu7Ns7oGrfLMk2uQ= > >
Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone
+1 Kazuaki Ishizaki "Weston Pace" wrote on 2021/06/30 18:52:46: > From: "Weston Pace" > To: dev@arrow.apache.org > Date: 2021/06/30 18:53 > Subject: [EXTERNAL] [VOTE] Arrow should state a convention for > encoding instants as Timestamp with "UTC" as the time zone > > This vote is a result of previous discussion[1][2]. This vote is also > a prerequisite for the PR in [5]. > > --- > Some date & time libraries have three temporal concepts. For the sake > of this document we will call them LocalDateTime, ZonedDateTime, and > Instant. An Instant is a timestamp that has no meaningful reference > time zone (e.g. events that did not occur on Earth or columns of > timestamps spanning more than one time zone). For more extensive > definitions and a discussion of their semantics and uses see [3]. > Currently Arrow describes how to encode two of these three concepts > into a Timestamp column and there is no guideline on how to store an > Instant. > > > This proposal states that Arrow should recommend that instants be encoded > into timestamp columns by setting the timezone string to "UTC". > --- > > For sample arguments (currently grouped as "for changing schema.fbs" > and "against changing schema.fbs") see [4]. For a detailed definition > of the terms LocalDateTime, ZonedDateTime, and Instant and a > discussion of their semantics see [3]. For a straw poll on > possible ways to handle instants see [2]. > > This vote will be open for at least 72 hours. > > [ ] +1 Update schema.fbs to state the above convention > [ ] +0 > [ ] -1 Do not make any change > > [1] INVALID URI REMOVED > u=https-3A__lists.apache.org_thread.html_r8216e5de3efd2935e3907ad9bd20ce07e430952f84de69b36337e5eb-2540-253Cdev.arrow.apache.org-253E=DwIBaQ=jf_iaSHvJObTbx- > siA1ZOg=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f- > ZCGj9Pg=avV0JpLmaymMbxpZiYwNb9Yug7bj3PGiNYiJCM-x3kY=Ty-Oq- > Gfuo2KRdogmjFFOLvji5yQ0LrrBZWWO7hDufs= > [2] INVALID URI REMOVED > u=https-3A__lists.apache.org_thread.html_r1bdffc76537ae9c12c37396880087fee9c0eec9000bf6ed4c9850c44-2540-253Cdev.arrow.apache.org-253E=DwIBaQ=jf_iaSHvJObTbx- > siA1ZOg=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f- > ZCGj9Pg=avV0JpLmaymMbxpZiYwNb9Yug7bj3PGiNYiJCM- > x3kY=NyxlTSPly7kAqwMiuXS7BH0lZkK3W0VmVSvvRF-ANa8= > [3] INVALID URI REMOVED > u=https-3A__docs.google.com_document_d_1QDwX4ypfNvESc2ywcT1ygaf2Y1R8SmkpifMV7gpJdBI_edit-3Fusp-3Dsharing=DwIBaQ=jf_iaSHvJObTbx- > siA1ZOg=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f- > ZCGj9Pg=avV0JpLmaymMbxpZiYwNb9Yug7bj3PGiNYiJCM- > x3kY=opFrDCQFvlSmY31hxs8MDKLcUe3muSTaNXosFCaPX5U= > [4] INVALID URI REMOVED > u=https-3A__docs.google.com_document_d_1xEKRhs-2DGUSMwjMhgmQdnCNMXwZrA10226AcXRoP8g9E_edit-3Fusp-3Dsharing=DwIBaQ=jf_iaSHvJObTbx- > siA1ZOg=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f- > ZCGj9Pg=avV0JpLmaymMbxpZiYwNb9Yug7bj3PGiNYiJCM- > x3kY=fIjWMI0tuH57ffsGzpOX85d5Dd7TN4tT_h0cj1elNbw= > [5] INVALID URI REMOVED > u=https-3A__github.com_apache_arrow_pull_10629=DwIBaQ=jf_iaSHvJObTbx- > siA1ZOg=b70dG_9wpCdZSkBJahHYQ4IwKMdp2hQM29f- > ZCGj9Pg=avV0JpLmaymMbxpZiYwNb9Yug7bj3PGiNYiJCM- > x3kY=RQrwm8rHhpbx-6JbTZ4WMVpWGrUIu7Ns7oGrfLMk2uQ=
Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone
+1 (non-binding) ~Eduardo From: Rok Mihevc Sent: Thursday, July 1, 2021 4:21:49 AM To: dev@arrow.apache.org Subject: Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone +1 (non-binding) On Thu, Jul 1, 2021 at 6:40 AM Bryan Cutler wrote: > +1 non-binding > > On Wed, Jun 30, 2021, 2:53 AM Weston Pace wrote: > > > This vote is a result of previous discussion[1][2]. This vote is also > > a prerequisite for the PR in [5]. > > > > --- > > Some date & time libraries have three temporal concepts. For the sake > > of this document we will call them LocalDateTime, ZonedDateTime, and > > Instant. An Instant is a timestamp that has no meaningful reference > > time zone (e.g. events that did not occur on Earth or columns of > > timestamps spanning more than one time zone). For more extensive > > definitions and a discussion of their semantics and uses see [3]. > > Currently Arrow describes how to encode two of these three concepts > > into a Timestamp column and there is no guideline on how to store an > > Instant. > > > > > > This proposal states that Arrow should recommend that instants be encoded > > into timestamp columns by setting the timezone string to "UTC". > > --- > > > > For sample arguments (currently grouped as "for changing schema.fbs" > > and "against changing schema.fbs") see [4]. For a detailed definition > > of the terms LocalDateTime, ZonedDateTime, and Instant and a > > discussion of their semantics see [3]. For a straw poll on > > possible ways to handle instants see [2]. > > > > This vote will be open for at least 72 hours. > > > > [ ] +1 Update schema.fbs to state the above convention > > [ ] +0 > > [ ] -1 Do not make any change > > > > [1] > > > https://lists.apache.org/thread.html/r8216e5de3efd2935e3907ad9bd20ce07e430952f84de69b36337e5eb%40%3Cdev.arrow.apache.org%3E > > [2] > > > https://lists.apache.org/thread.html/r1bdffc76537ae9c12c37396880087fee9c0eec9000bf6ed4c9850c44%40%3Cdev.arrow.apache.org%3E > > [3] > > > https://docs.google.com/document/d/1QDwX4ypfNvESc2ywcT1ygaf2Y1R8SmkpifMV7gpJdBI/edit?usp=sharing > > [4] > > > https://docs.google.com/document/d/1xEKRhs-GUSMwjMhgmQdnCNMXwZrA10226AcXRoP8g9E/edit?usp=sharing > > [5] https://github.com/apache/arrow/pull/10629 > > >
Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone
+1 (non-binding) On Thu, Jul 1, 2021 at 6:40 AM Bryan Cutler wrote: > +1 non-binding > > On Wed, Jun 30, 2021, 2:53 AM Weston Pace wrote: > > > This vote is a result of previous discussion[1][2]. This vote is also > > a prerequisite for the PR in [5]. > > > > --- > > Some date & time libraries have three temporal concepts. For the sake > > of this document we will call them LocalDateTime, ZonedDateTime, and > > Instant. An Instant is a timestamp that has no meaningful reference > > time zone (e.g. events that did not occur on Earth or columns of > > timestamps spanning more than one time zone). For more extensive > > definitions and a discussion of their semantics and uses see [3]. > > Currently Arrow describes how to encode two of these three concepts > > into a Timestamp column and there is no guideline on how to store an > > Instant. > > > > > > This proposal states that Arrow should recommend that instants be encoded > > into timestamp columns by setting the timezone string to "UTC". > > --- > > > > For sample arguments (currently grouped as "for changing schema.fbs" > > and "against changing schema.fbs") see [4]. For a detailed definition > > of the terms LocalDateTime, ZonedDateTime, and Instant and a > > discussion of their semantics see [3]. For a straw poll on > > possible ways to handle instants see [2]. > > > > This vote will be open for at least 72 hours. > > > > [ ] +1 Update schema.fbs to state the above convention > > [ ] +0 > > [ ] -1 Do not make any change > > > > [1] > > > https://lists.apache.org/thread.html/r8216e5de3efd2935e3907ad9bd20ce07e430952f84de69b36337e5eb%40%3Cdev.arrow.apache.org%3E > > [2] > > > https://lists.apache.org/thread.html/r1bdffc76537ae9c12c37396880087fee9c0eec9000bf6ed4c9850c44%40%3Cdev.arrow.apache.org%3E > > [3] > > > https://docs.google.com/document/d/1QDwX4ypfNvESc2ywcT1ygaf2Y1R8SmkpifMV7gpJdBI/edit?usp=sharing > > [4] > > > https://docs.google.com/document/d/1xEKRhs-GUSMwjMhgmQdnCNMXwZrA10226AcXRoP8g9E/edit?usp=sharing > > [5] https://github.com/apache/arrow/pull/10629 > > >
Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone
+1 non-binding On Wed, Jun 30, 2021, 2:53 AM Weston Pace wrote: > This vote is a result of previous discussion[1][2]. This vote is also > a prerequisite for the PR in [5]. > > --- > Some date & time libraries have three temporal concepts. For the sake > of this document we will call them LocalDateTime, ZonedDateTime, and > Instant. An Instant is a timestamp that has no meaningful reference > time zone (e.g. events that did not occur on Earth or columns of > timestamps spanning more than one time zone). For more extensive > definitions and a discussion of their semantics and uses see [3]. > Currently Arrow describes how to encode two of these three concepts > into a Timestamp column and there is no guideline on how to store an > Instant. > > > This proposal states that Arrow should recommend that instants be encoded > into timestamp columns by setting the timezone string to "UTC". > --- > > For sample arguments (currently grouped as "for changing schema.fbs" > and "against changing schema.fbs") see [4]. For a detailed definition > of the terms LocalDateTime, ZonedDateTime, and Instant and a > discussion of their semantics see [3]. For a straw poll on > possible ways to handle instants see [2]. > > This vote will be open for at least 72 hours. > > [ ] +1 Update schema.fbs to state the above convention > [ ] +0 > [ ] -1 Do not make any change > > [1] > https://lists.apache.org/thread.html/r8216e5de3efd2935e3907ad9bd20ce07e430952f84de69b36337e5eb%40%3Cdev.arrow.apache.org%3E > [2] > https://lists.apache.org/thread.html/r1bdffc76537ae9c12c37396880087fee9c0eec9000bf6ed4c9850c44%40%3Cdev.arrow.apache.org%3E > [3] > https://docs.google.com/document/d/1QDwX4ypfNvESc2ywcT1ygaf2Y1R8SmkpifMV7gpJdBI/edit?usp=sharing > [4] > https://docs.google.com/document/d/1xEKRhs-GUSMwjMhgmQdnCNMXwZrA10226AcXRoP8g9E/edit?usp=sharing > [5] https://github.com/apache/arrow/pull/10629 >
Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone
+1 On Wed, Jun 30, 2021 at 9:25 AM Benjamin Kietzman wrote: > +1 > > On Wed, Jun 30, 2021, 08:54 David Li wrote: > > > +1 > > > > On Wed, Jun 30, 2021, at 08:46, Wes McKinney wrote: > > > +1 > > > > > > On Wed, Jun 30, 2021 at 12:03 PM Antoine Pitrou > > wrote: > > > > > > > > +1 > > > > > > > > > > > > Le 30/06/2021 à 11:52, Weston Pace a écrit : > > > > > This vote is a result of previous discussion[1][2]. This vote is > > also > > > > > a prerequisite for the PR in [5]. > > > > > > > > > > --- > > > > > Some date & time libraries have three temporal concepts. For the > > sake > > > > > of this document we will call them LocalDateTime, ZonedDateTime, > and > > > > > Instant. An Instant is a timestamp that has no meaningful > reference > > > > > time zone (e.g. events that did not occur on Earth or columns of > > > > > timestamps spanning more than one time zone). For more extensive > > > > > definitions and a discussion of their semantics and uses see [3]. > > > > > Currently Arrow describes how to encode two of these three concepts > > > > > into a Timestamp column and there is no guideline on how to store > an > > > > > Instant. > > > > > > > > > > > > > > > This proposal states that Arrow should recommend that instants be > > encoded > > > > > into timestamp columns by setting the timezone string to "UTC". > > > > > --- > > > > > > > > > > For sample arguments (currently grouped as "for changing > schema.fbs" > > > > > and "against changing schema.fbs") see [4]. For a detailed > > definition > > > > > of the terms LocalDateTime, ZonedDateTime, and Instant and a > > > > > discussion of their semantics see [3]. For a straw poll on > > > > > possible ways to handle instants see [2]. > > > > > > > > > > This vote will be open for at least 72 hours. > > > > > > > > > > [ ] +1 Update schema.fbs to state the above convention > > > > > [ ] +0 > > > > > [ ] -1 Do not make any change > > > > > > > > > > [1] > > > https://lists.apache.org/thread.html/r8216e5de3efd2935e3907ad9bd20ce07e430952f84de69b36337e5eb%40%3Cdev.arrow.apache.org%3E > > > > > [2] > > > https://lists.apache.org/thread.html/r1bdffc76537ae9c12c37396880087fee9c0eec9000bf6ed4c9850c44%40%3Cdev.arrow.apache.org%3E > > > > > [3] > > > https://docs.google.com/document/d/1QDwX4ypfNvESc2ywcT1ygaf2Y1R8SmkpifMV7gpJdBI/edit?usp=sharing > > > > > [4] > > > https://docs.google.com/document/d/1xEKRhs-GUSMwjMhgmQdnCNMXwZrA10226AcXRoP8g9E/edit?usp=sharing > > > > > [5] https://github.com/apache/arrow/pull/10629 > > > > > > > > >
Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone
+1 On Wed, Jun 30, 2021, 08:54 David Li wrote: > +1 > > On Wed, Jun 30, 2021, at 08:46, Wes McKinney wrote: > > +1 > > > > On Wed, Jun 30, 2021 at 12:03 PM Antoine Pitrou > wrote: > > > > > > +1 > > > > > > > > > Le 30/06/2021 à 11:52, Weston Pace a écrit : > > > > This vote is a result of previous discussion[1][2]. This vote is > also > > > > a prerequisite for the PR in [5]. > > > > > > > > --- > > > > Some date & time libraries have three temporal concepts. For the > sake > > > > of this document we will call them LocalDateTime, ZonedDateTime, and > > > > Instant. An Instant is a timestamp that has no meaningful reference > > > > time zone (e.g. events that did not occur on Earth or columns of > > > > timestamps spanning more than one time zone). For more extensive > > > > definitions and a discussion of their semantics and uses see [3]. > > > > Currently Arrow describes how to encode two of these three concepts > > > > into a Timestamp column and there is no guideline on how to store an > > > > Instant. > > > > > > > > > > > > This proposal states that Arrow should recommend that instants be > encoded > > > > into timestamp columns by setting the timezone string to "UTC". > > > > --- > > > > > > > > For sample arguments (currently grouped as "for changing schema.fbs" > > > > and "against changing schema.fbs") see [4]. For a detailed > definition > > > > of the terms LocalDateTime, ZonedDateTime, and Instant and a > > > > discussion of their semantics see [3]. For a straw poll on > > > > possible ways to handle instants see [2]. > > > > > > > > This vote will be open for at least 72 hours. > > > > > > > > [ ] +1 Update schema.fbs to state the above convention > > > > [ ] +0 > > > > [ ] -1 Do not make any change > > > > > > > > [1] > https://lists.apache.org/thread.html/r8216e5de3efd2935e3907ad9bd20ce07e430952f84de69b36337e5eb%40%3Cdev.arrow.apache.org%3E > > > > [2] > https://lists.apache.org/thread.html/r1bdffc76537ae9c12c37396880087fee9c0eec9000bf6ed4c9850c44%40%3Cdev.arrow.apache.org%3E > > > > [3] > https://docs.google.com/document/d/1QDwX4ypfNvESc2ywcT1ygaf2Y1R8SmkpifMV7gpJdBI/edit?usp=sharing > > > > [4] > https://docs.google.com/document/d/1xEKRhs-GUSMwjMhgmQdnCNMXwZrA10226AcXRoP8g9E/edit?usp=sharing > > > > [5] https://github.com/apache/arrow/pull/10629 > > > > > >
Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone
+1 On Wed, Jun 30, 2021, at 08:46, Wes McKinney wrote: > +1 > > On Wed, Jun 30, 2021 at 12:03 PM Antoine Pitrou wrote: > > > > +1 > > > > > > Le 30/06/2021 à 11:52, Weston Pace a écrit : > > > This vote is a result of previous discussion[1][2]. This vote is also > > > a prerequisite for the PR in [5]. > > > > > > --- > > > Some date & time libraries have three temporal concepts. For the sake > > > of this document we will call them LocalDateTime, ZonedDateTime, and > > > Instant. An Instant is a timestamp that has no meaningful reference > > > time zone (e.g. events that did not occur on Earth or columns of > > > timestamps spanning more than one time zone). For more extensive > > > definitions and a discussion of their semantics and uses see [3]. > > > Currently Arrow describes how to encode two of these three concepts > > > into a Timestamp column and there is no guideline on how to store an > > > Instant. > > > > > > > > > This proposal states that Arrow should recommend that instants be encoded > > > into timestamp columns by setting the timezone string to "UTC". > > > --- > > > > > > For sample arguments (currently grouped as "for changing schema.fbs" > > > and "against changing schema.fbs") see [4]. For a detailed definition > > > of the terms LocalDateTime, ZonedDateTime, and Instant and a > > > discussion of their semantics see [3]. For a straw poll on > > > possible ways to handle instants see [2]. > > > > > > This vote will be open for at least 72 hours. > > > > > > [ ] +1 Update schema.fbs to state the above convention > > > [ ] +0 > > > [ ] -1 Do not make any change > > > > > > [1] > > > https://lists.apache.org/thread.html/r8216e5de3efd2935e3907ad9bd20ce07e430952f84de69b36337e5eb%40%3Cdev.arrow.apache.org%3E > > > [2] > > > https://lists.apache.org/thread.html/r1bdffc76537ae9c12c37396880087fee9c0eec9000bf6ed4c9850c44%40%3Cdev.arrow.apache.org%3E > > > [3] > > > https://docs.google.com/document/d/1QDwX4ypfNvESc2ywcT1ygaf2Y1R8SmkpifMV7gpJdBI/edit?usp=sharing > > > [4] > > > https://docs.google.com/document/d/1xEKRhs-GUSMwjMhgmQdnCNMXwZrA10226AcXRoP8g9E/edit?usp=sharing > > > [5] https://github.com/apache/arrow/pull/10629 > > > >
Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone
+1 On Wed, Jun 30, 2021 at 12:03 PM Antoine Pitrou wrote: > > +1 > > > Le 30/06/2021 à 11:52, Weston Pace a écrit : > > This vote is a result of previous discussion[1][2]. This vote is also > > a prerequisite for the PR in [5]. > > > > --- > > Some date & time libraries have three temporal concepts. For the sake > > of this document we will call them LocalDateTime, ZonedDateTime, and > > Instant. An Instant is a timestamp that has no meaningful reference > > time zone (e.g. events that did not occur on Earth or columns of > > timestamps spanning more than one time zone). For more extensive > > definitions and a discussion of their semantics and uses see [3]. > > Currently Arrow describes how to encode two of these three concepts > > into a Timestamp column and there is no guideline on how to store an > > Instant. > > > > > > This proposal states that Arrow should recommend that instants be encoded > > into timestamp columns by setting the timezone string to "UTC". > > --- > > > > For sample arguments (currently grouped as "for changing schema.fbs" > > and "against changing schema.fbs") see [4]. For a detailed definition > > of the terms LocalDateTime, ZonedDateTime, and Instant and a > > discussion of their semantics see [3]. For a straw poll on > > possible ways to handle instants see [2]. > > > > This vote will be open for at least 72 hours. > > > > [ ] +1 Update schema.fbs to state the above convention > > [ ] +0 > > [ ] -1 Do not make any change > > > > [1] > > https://lists.apache.org/thread.html/r8216e5de3efd2935e3907ad9bd20ce07e430952f84de69b36337e5eb%40%3Cdev.arrow.apache.org%3E > > [2] > > https://lists.apache.org/thread.html/r1bdffc76537ae9c12c37396880087fee9c0eec9000bf6ed4c9850c44%40%3Cdev.arrow.apache.org%3E > > [3] > > https://docs.google.com/document/d/1QDwX4ypfNvESc2ywcT1ygaf2Y1R8SmkpifMV7gpJdBI/edit?usp=sharing > > [4] > > https://docs.google.com/document/d/1xEKRhs-GUSMwjMhgmQdnCNMXwZrA10226AcXRoP8g9E/edit?usp=sharing > > [5] https://github.com/apache/arrow/pull/10629 > >
Re: [VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone
+1 Le 30/06/2021 à 11:52, Weston Pace a écrit : This vote is a result of previous discussion[1][2]. This vote is also a prerequisite for the PR in [5]. --- Some date & time libraries have three temporal concepts. For the sake of this document we will call them LocalDateTime, ZonedDateTime, and Instant. An Instant is a timestamp that has no meaningful reference time zone (e.g. events that did not occur on Earth or columns of timestamps spanning more than one time zone). For more extensive definitions and a discussion of their semantics and uses see [3]. Currently Arrow describes how to encode two of these three concepts into a Timestamp column and there is no guideline on how to store an Instant. This proposal states that Arrow should recommend that instants be encoded into timestamp columns by setting the timezone string to "UTC". --- For sample arguments (currently grouped as "for changing schema.fbs" and "against changing schema.fbs") see [4]. For a detailed definition of the terms LocalDateTime, ZonedDateTime, and Instant and a discussion of their semantics see [3]. For a straw poll on possible ways to handle instants see [2]. This vote will be open for at least 72 hours. [ ] +1 Update schema.fbs to state the above convention [ ] +0 [ ] -1 Do not make any change [1] https://lists.apache.org/thread.html/r8216e5de3efd2935e3907ad9bd20ce07e430952f84de69b36337e5eb%40%3Cdev.arrow.apache.org%3E [2] https://lists.apache.org/thread.html/r1bdffc76537ae9c12c37396880087fee9c0eec9000bf6ed4c9850c44%40%3Cdev.arrow.apache.org%3E [3] https://docs.google.com/document/d/1QDwX4ypfNvESc2ywcT1ygaf2Y1R8SmkpifMV7gpJdBI/edit?usp=sharing [4] https://docs.google.com/document/d/1xEKRhs-GUSMwjMhgmQdnCNMXwZrA10226AcXRoP8g9E/edit?usp=sharing [5] https://github.com/apache/arrow/pull/10629
[VOTE] Arrow should state a convention for encoding instants as Timestamp with "UTC" as the time zone
This vote is a result of previous discussion[1][2]. This vote is also a prerequisite for the PR in [5]. --- Some date & time libraries have three temporal concepts. For the sake of this document we will call them LocalDateTime, ZonedDateTime, and Instant. An Instant is a timestamp that has no meaningful reference time zone (e.g. events that did not occur on Earth or columns of timestamps spanning more than one time zone). For more extensive definitions and a discussion of their semantics and uses see [3]. Currently Arrow describes how to encode two of these three concepts into a Timestamp column and there is no guideline on how to store an Instant. This proposal states that Arrow should recommend that instants be encoded into timestamp columns by setting the timezone string to "UTC". --- For sample arguments (currently grouped as "for changing schema.fbs" and "against changing schema.fbs") see [4]. For a detailed definition of the terms LocalDateTime, ZonedDateTime, and Instant and a discussion of their semantics see [3]. For a straw poll on possible ways to handle instants see [2]. This vote will be open for at least 72 hours. [ ] +1 Update schema.fbs to state the above convention [ ] +0 [ ] -1 Do not make any change [1] https://lists.apache.org/thread.html/r8216e5de3efd2935e3907ad9bd20ce07e430952f84de69b36337e5eb%40%3Cdev.arrow.apache.org%3E [2] https://lists.apache.org/thread.html/r1bdffc76537ae9c12c37396880087fee9c0eec9000bf6ed4c9850c44%40%3Cdev.arrow.apache.org%3E [3] https://docs.google.com/document/d/1QDwX4ypfNvESc2ywcT1ygaf2Y1R8SmkpifMV7gpJdBI/edit?usp=sharing [4] https://docs.google.com/document/d/1xEKRhs-GUSMwjMhgmQdnCNMXwZrA10226AcXRoP8g9E/edit?usp=sharing [5] https://github.com/apache/arrow/pull/10629
