drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sudheeshkatkam <...@git.apache.org>
Subject [GitHub] drill issue #639: DRILL-4706: Fragment planning causes Drillbits to read rem...
Date Fri, 04 Nov 2016 20:46:06 GMT
Github user sudheeshkatkam commented on the issue:

    Hmm the answer seems like a rephrasing of the question. Sorry, I misspoke. Better asked:
    The issue is regarding assigning **_work to_** fragments based on strict locality (**_decide
which fragment does what_**). So why is the parallelization (**_decide how many fragments_**)
logic affected?

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message