That's right. Thanks Alan.

On Tue, Jul 22, 2008 at 11:56 PM, Alan Gates <[EMAIL PROTECTED]> wrote:

> Are you thinking of getWritableComparableTypes and getPigType?  We can move
> those into a separate file and then put them in the backend specific area.
>
> I also noticed I missed Launcher, MapReduceLauncher, and LocalLauncher, all
> of which are now under backend.hadoop.executionengine.  I need to move
> LocalLauncher to backend.local.executionengine and Launcher to
> backend.executionengine.  I'll do that later this week, but I don't think it
> will affect anyone as I'm the only one working in that code at the moment.
>
> Alan.
>
>
> pi song wrote:
>
>> This reminds me that some methods in DataType class are still backend
>> specific.
>>
>> On Tue, Jul 22, 2008 at 3:32 AM, Alan Gates <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>>> Over the weekend I moved a bunch of code around in the types branch.
>>>  During development much of the code had grown here and there without
>>> sufficient attention to where packages actually belonged.  So, I've
>>> corrected that.
>>>
>>> impl/mapReduceLayer has moved to
>>> backend/hadoop/executionengine/mapReduceLayer, since it is hadoop
>>> specific.
>>> impl/physicalLayer has similarly moved to
>>> backend/hadoop/executionengine/physicalLayer.
>>> impl/logicalLayer/LogToPhyTranslator.java has been moved into the
>>> physicalLayer package, since it is backend specific.
>>> impl/plan/MultiMap.java has moved into impl/util since it is generic.
>>>
>>> Now, hopefully, all backend specific functionality is once again under
>>> backend and everything under impl and data are generic.
>>>
>>> Alan.
>>>
>>>
>>>
>>
>>
>>
>

Reply via email to