Re: "Death of Schema-on-Read"

On Thu, Apr 5, 2018 at 9:43 PM, Paul Rogers wrote: > Great discussion. Really appreciate the insight from the Drill users! > > To Ted's points: the simplest possible solution is to allow a table > function to express types. Just making stuff up: > > SELECT a FROM

Re: "Death of Schema-on-Read"

On Thu, Apr 5, 2018 at 10:22 PM, Hanumath Rao Maduri wrote: > ... > > Thank you Ted for your valuable suggestions, as regards to your comment on > "metastore is good but centralized is bad" can you please share your view > point on what all design issues it can cause. I know

Re: "Death of Schema-on-Read"

Hi Hanu, Sorry, I tossed in a new topic late in the discussion. We started by noting that views don't always work to resolve low-level schema conflicts for the reasons we discussed, so we need something else. That led to the schema hint discussion. The additional point I raised was that views

[GitHub] drill issue #1203: DRILL-6289: Cluster view should show more relevant inform...

Github user kkhatua commented on the issue: https://github.com/apache/drill/pull/1203 @arina-ielchiieva could you please review this? ---

[GitHub] drill pull request #1203: DRILL-6289: Cluster view should show more relevant...

GitHub user kkhatua opened a pull request: https://github.com/apache/drill/pull/1203 DRILL-6289: Cluster view should show more relevant information The commits make use of AJAX calls by the browser to all the Drillbits for status metrics, which are then displayed here. This works

Re: "Death of Schema-on-Read"

Hello, Thanks for Ted & Paul for clarifying my questions. Sorry for not being clear in my previous post, When I said create view I was under the impression for simple views where we use cast expressions currently to cast them to types. In this case planner can use this information to force the

[GitHub] drill issue #1203: DRILL-6289: Cluster view should show more relevant inform...

Github user kkhatua commented on the issue: https://github.com/apache/drill/pull/1203 **Snapshot:**  ---

Re: "Death of Schema-on-Read"

Hi Hanu, The problem with views as is, even with casts, is that the casting comes too late to resolve he issues I highlighted in earlier messages. Ted's cast push-down idea causes the conversion to happen at read time so that we can, say, cast a string to an int, or cast a null to the proper

Re: "Death of Schema-on-Read"

Ted, this is why your participation in Drill is such a gift: cast push-down is an elegant, simple solution that even works in views. Beautiful. Thanks, - Paul On Friday, April 6, 2018, 11:35:37 AM PDT, Ted Dunning wrote: On Thu, Apr 5, 2018 at 9:43 PM, Paul

Re: "Death of Schema-on-Read"

Hi Aman, As we get into details, I suggested to Hanu that we move the discussion into a JIRA ticket. >On the subject of CAST pushdown to Scans, there are potential drawbacks  >  - In general, the planner will see a Scan-Project where the Project has  CAST functions.  But the Project can have

[GitHub] drill issue #1203: DRILL-6289: Cluster view should show more relevant inform...

Github user kkhatua commented on the issue: https://github.com/apache/drill/pull/1203 **PopOut to open in new window:**  Tooltip describing the new columns

Re: "Death of Schema-on-Read"

On the subject of CAST pushdown to Scans, there are potential drawbacks ... - In general, the planner will see a Scan-Project where the Project has CAST functions. But the Project can have arbitrary expressions, e.g CAST(a as INT) * 5 or a combination of 2 CAST functions or non-CAST

[GitHub] drill issue #1199: DRILL-6303: Provide a button to copy the Drillbit's JStac...

Github user arina-ielchiieva commented on the issue: https://github.com/apache/drill/pull/1199 +1 ---

[GitHub] drill issue #1197: DRILL-6279: UI indicates operators that spilled in-memory...

Github user arina-ielchiieva commented on the issue: https://github.com/apache/drill/pull/1197 +1 ---