You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by Daniel Barclay <db...@maprtech.com> on 2015/04/06 22:20:20 UTC
drill-interpreter project errors
What's going on with the drill-interpreter module?
For while now, in Eclipse it shows up as having errors (e.g., that
org.apache.drill.BaseTestQuery is unknown), even after I issue the Maven -> Update
Project ... command on it.
Daniel
--
Daniel Barclay
MapR Technologies
Re: drill-interpreter project errors
Posted by Daniel Barclay <db...@maprtech.com>.
Chris Westin wrote:
> That's not going to remove the project from your IDE.
Of course, but shouldn't it have deleted all the files from Git?
Daniel
> When I saw Jason's
> commit went through, I removed the project, updated maven modules metadata,
> and rebuilt after the next time I rebased. Then all was well.
>
> On Mon, Apr 6, 2015 at 1:52 PM, Daniel Barclay <db...@maprtech.com>
> wrote:
>
>> You can safely delete the module from your working directory.
>>>
>>
>> Thanks.
>>
>> Why didn't my rebasing of my branch on master remove the module?
>>
>> Daniel
>>
>>
>> Jason Altekruse wrote:
>>
>>> The interpreter module was removed in a recent commit to make the
>>> interpreter usable at planning time.
>>>
>>> The interpreter code was committed a few months ago, but only had unit
>>> tests written against it in its own module. To make the interpreter work
>>> with the other modules and hook it up to planning rules it needed to be
>>> refactored, the way we chose to refactor it actually removed the need for
>>> the separate module and build step. You can safely delete the module from
>>> your working directory.
>>>
>>> https://github.com/apache/drill/commit/0aa8b19d624d173da51de36aa164f3
>>> 435d3366a4
>>>
>>> -Jason Altekruse
>>>
>>> On Mon, Apr 6, 2015 at 1:20 PM, Daniel Barclay <db...@maprtech.com>
>>> wrote:
>>>
>>> What's going on with the drill-interpreter module?
>>>>
>>>> For while now, in Eclipse it shows up as having errors (e.g., that
>>>> org.apache.drill.BaseTestQuery is unknown), even after I issue the Maven
>>>> -> Update
>>>> Project ... command on it.
>>>>
>>>>
>>>> Daniel
>>>> --
>>>> Daniel Barclay
>>>> MapR Technologies
>>>>
>>>>
>>
>> --
>> Daniel Barclay
>> MapR Technologies
>>
>>
>
--
Daniel Barclay
MapR Technologies
Re: drill-interpreter project errors
Posted by Chris Westin <ch...@gmail.com>.
That's not going to remove the project from your IDE. When I saw Jason's
commit went through, I removed the project, updated maven modules metadata,
and rebuilt after the next time I rebased. Then all was well.
On Mon, Apr 6, 2015 at 1:52 PM, Daniel Barclay <db...@maprtech.com>
wrote:
> You can safely delete the module from your working directory.
>>
>
> Thanks.
>
> Why didn't my rebasing of my branch on master remove the module?
>
> Daniel
>
>
> Jason Altekruse wrote:
>
>> The interpreter module was removed in a recent commit to make the
>> interpreter usable at planning time.
>>
>> The interpreter code was committed a few months ago, but only had unit
>> tests written against it in its own module. To make the interpreter work
>> with the other modules and hook it up to planning rules it needed to be
>> refactored, the way we chose to refactor it actually removed the need for
>> the separate module and build step. You can safely delete the module from
>> your working directory.
>>
>> https://github.com/apache/drill/commit/0aa8b19d624d173da51de36aa164f3
>> 435d3366a4
>>
>> -Jason Altekruse
>>
>> On Mon, Apr 6, 2015 at 1:20 PM, Daniel Barclay <db...@maprtech.com>
>> wrote:
>>
>> What's going on with the drill-interpreter module?
>>>
>>> For while now, in Eclipse it shows up as having errors (e.g., that
>>> org.apache.drill.BaseTestQuery is unknown), even after I issue the Maven
>>> -> Update
>>> Project ... command on it.
>>>
>>>
>>> Daniel
>>> --
>>> Daniel Barclay
>>> MapR Technologies
>>>
>>>
>
> --
> Daniel Barclay
> MapR Technologies
>
>
Re: drill-interpreter project errors
Posted by Chris Westin <cw...@yahoo.com>.
That's not going to remove the project from your IDE. When I saw Jason's
commit went through, I removed the project, updated maven modules metadata,
and rebuilt after the next time I rebased. Then all was well.
On Mon, Apr 6, 2015 at 1:52 PM, Daniel Barclay <db...@maprtech.com>
wrote:
> You can safely delete the module from your working directory.
>>
>
> Thanks.
>
> Why didn't my rebasing of my branch on master remove the module?
>
> Daniel
>
>
> Jason Altekruse wrote:
>
>> The interpreter module was removed in a recent commit to make the
>> interpreter usable at planning time.
>>
>> The interpreter code was committed a few months ago, but only had unit
>> tests written against it in its own module. To make the interpreter work
>> with the other modules and hook it up to planning rules it needed to be
>> refactored, the way we chose to refactor it actually removed the need for
>> the separate module and build step. You can safely delete the module from
>> your working directory.
>>
>> https://github.com/apache/drill/commit/0aa8b19d624d173da51de36aa164f3
>> 435d3366a4
>>
>> -Jason Altekruse
>>
>> On Mon, Apr 6, 2015 at 1:20 PM, Daniel Barclay <db...@maprtech.com>
>> wrote:
>>
>> What's going on with the drill-interpreter module?
>>>
>>> For while now, in Eclipse it shows up as having errors (e.g., that
>>> org.apache.drill.BaseTestQuery is unknown), even after I issue the Maven
>>> -> Update
>>> Project ... command on it.
>>>
>>>
>>> Daniel
>>> --
>>> Daniel Barclay
>>> MapR Technologies
>>>
>>>
>
> --
> Daniel Barclay
> MapR Technologies
>
>
Re: drill-interpreter project errors
Posted by Daniel Barclay <db...@maprtech.com>.
> You can safely delete the module from your working directory.
Thanks.
Why didn't my rebasing of my branch on master remove the module?
Daniel
Jason Altekruse wrote:
> The interpreter module was removed in a recent commit to make the
> interpreter usable at planning time.
>
> The interpreter code was committed a few months ago, but only had unit
> tests written against it in its own module. To make the interpreter work
> with the other modules and hook it up to planning rules it needed to be
> refactored, the way we chose to refactor it actually removed the need for
> the separate module and build step. You can safely delete the module from
> your working directory.
>
> https://github.com/apache/drill/commit/0aa8b19d624d173da51de36aa164f3435d3366a4
>
> -Jason Altekruse
>
> On Mon, Apr 6, 2015 at 1:20 PM, Daniel Barclay <db...@maprtech.com>
> wrote:
>
>> What's going on with the drill-interpreter module?
>>
>> For while now, in Eclipse it shows up as having errors (e.g., that
>> org.apache.drill.BaseTestQuery is unknown), even after I issue the Maven
>> -> Update
>> Project ... command on it.
>>
>>
>> Daniel
>> --
>> Daniel Barclay
>> MapR Technologies
>>
--
Daniel Barclay
MapR Technologies
Re: drill-interpreter project errors
Posted by Jason Altekruse <al...@gmail.com>.
The interpreter module was removed in a recent commit to make the
interpreter usable at planning time.
The interpreter code was committed a few months ago, but only had unit
tests written against it in its own module. To make the interpreter work
with the other modules and hook it up to planning rules it needed to be
refactored, the way we chose to refactor it actually removed the need for
the separate module and build step. You can safely delete the module from
your working directory.
https://github.com/apache/drill/commit/0aa8b19d624d173da51de36aa164f3435d3366a4
-Jason Altekruse
On Mon, Apr 6, 2015 at 1:20 PM, Daniel Barclay <db...@maprtech.com>
wrote:
> What's going on with the drill-interpreter module?
>
> For while now, in Eclipse it shows up as having errors (e.g., that
> org.apache.drill.BaseTestQuery is unknown), even after I issue the Maven
> -> Update
> Project ... command on it.
>
>
> Daniel
> --
> Daniel Barclay
> MapR Technologies
>