Hi,
I am using Drill to query Parquet files that have fields of type
timestamp_micros. By default, Drill truncates those microsecond
values to milliseconds when reading the Parquet files in order to convert them
to SQL timestamps.
In some of my use cases I need to read the original microsecond
I received notice today that the DFDL OGF standard is officially headed to
become an ISO standard. The ballot within ISO JTC1 passed 100%.
I will let you know more info when I get it about how we can propagate this
information, any branding considerations ISO JTC1 requires about it, their
trademar
Nice!
> On Jan 22, 2024, at 08:44, Mike Beckerle wrote:
>
> I received notice today that the DFDL OGF standard is officially headed to
> become an ISO standard. The ballot within ISO JTC1 passed 100%.
>
> I will let you know more info when I get it about how we can propagate this
> information,
Hi Peter,
It sounds like you are on the right track: the new option is the quick
short-term solution. The best long-term solution is to generalize Drill's
date/time type, but that would take much more work. (Drill also has a bug
where the treatment of timezones is incorrect, which forces Drill to
yaozhu opened a new issue, #2873:
URL: https://github.com/apache/drill/issues/2873
mysql table baseall and table test has the same tale struct and recored
show create table baseall;
+-+-
cgivre commented on issue #2873:
URL: https://github.com/apache/drill/issues/2873#issuecomment-1905101608
Can you please provide a screenshot or some explanation that is more clear?
This is really difficult to follow.
--
This is an automated message from the Apache Git Service.
To respon
yaozhu commented on issue #2873:
URL: https://github.com/apache/drill/issues/2873#issuecomment-1905105700
> Can you please provide a screenshot or some explanation that is more
clear? This is really difficult to follow.
cgivre commented on issue #2874:
URL: https://github.com/apache/drill/issues/2874#issuecomment-1905299722
@shfshihuafeng Can you please submit this as a pull request?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use th
shfshihuafeng commented on issue #2871:
URL: https://github.com/apache/drill/issues/2871#issuecomment-1905300921
> @weijunlu, you may have found a bug. The behavior you described is not
expected.
>
> Just to verify I understand: you ran your query once. Did the query run
successfully
shfshihuafeng commented on issue #2874:
URL: https://github.com/apache/drill/issues/2874#issuecomment-1905301573
ok @cgivre
--
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 comme
shihuafeng created DRILL-8478:
-
Summary: mergejion memory leak when exception
Key: DRILL-8478
URL: https://issues.apache.org/jira/browse/DRILL-8478
Project: Apache Drill
Issue Type: Bug
shfshihuafeng opened a new pull request, #2875:
URL: https://github.com/apache/drill/pull/2875
# [DRILL-](https://issues.apache.org/jira/browse/DRILL-): PR Title
DRILL-8478. HashPartition memory leak when it allocate memory exception with
OutOfMemoryException (#2874)
##
paul-rogers commented on code in PR #2875:
URL: https://github.com/apache/drill/pull/2875#discussion_r1462817821
##
exec/java-exec/src/main/java/org/apache/drill/exec/physical/impl/common/HashPartition.java:
##
@@ -157,11 +162,11 @@ public HashPartition(FragmentContext context,
paul-rogers commented on code in PR #2875:
URL: https://github.com/apache/drill/pull/2875#discussion_r1462817821
##
exec/java-exec/src/main/java/org/apache/drill/exec/physical/impl/common/HashPartition.java:
##
@@ -157,11 +162,11 @@ public HashPartition(FragmentContext context,
shfshihuafeng commented on code in PR #2875:
URL: https://github.com/apache/drill/pull/2875#discussion_r1462854154
##
exec/java-exec/src/main/java/org/apache/drill/exec/physical/impl/common/HashPartition.java:
##
@@ -157,11 +162,11 @@ public HashPartition(FragmentContext context
21 matches
Mail list logo
