ok, thank you very much.

2010/10/15 Carl Steinbach <c...@cloudera.com>

> Hi,
>
> HIVE-1681 does not require any changes to the database schema. It is
> strictly
> a code change.
>
> Carl
>
>
> On Thu, Oct 14, 2010 at 11:19 PM, lei liu <liulei...@gmail.com> wrote:
>
>> Hi Carl Steinbach,
>>
>> Could you tell me this issues will result in the database structure is
>> changed?
>>
>>
>> 2010/10/15 Carl Steinbach <c...@cloudera.com>
>>
>>> Hi LiuLei,
>>>
>>> We plan to make one more change to the metastore code (HIVE-1681) before
>>> building the 0.6 release. I expect that the patch for HIVE-1681 will get
>>> committed
>>> to trunk and the 0.6 branch sometime in the next couple of days. You can
>>> track
>>> progress on the list of unresolved 0.6 blockers on the following webpage:
>>>
>>>
>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310843&fixfor=12314524
>>>
>>> Thanks.
>>>
>>> Carl
>>>
>>> On Thu, Oct 14, 2010 at 7:53 PM, lei liu <liulei...@gmail.com> wrote:
>>>
>>>> Hi Carl Steinbach ,
>>>>
>>>> Thank you for your reply quickly.
>>>>
>>>> I look the metastore code is updated in 06/Oct/10 (please see 
>>>> HIVE-1364<https://issues.apache.org/jira/browse/HIVE-1364> issues),
>>>> could you tell me whether the metasote code in svn will not be updated 
>>>> again
>>>> when hive0.6 is released?
>>>>
>>>> Thanks,
>>>>
>>>> LiuLei
>>>>
>>>> 2010/10/15 Carl Steinbach <c...@cloudera.com>
>>>>
>>>> Hi,
>>>>>
>>>>> We're working on building the first release candidate for 0.6. I expect
>>>>> that
>>>>> the official release will happen soon, but I can't promise that it will
>>>>> occur it in the next week.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Carl
>>>>>
>>>>>
>>>>> On Thu, Oct 14, 2010 at 7:30 PM, lei liu <liulei...@gmail.com> wrote:
>>>>>
>>>>>> This month our system will be released, so I want to use newest
>>>>>> hive0.6 version, I want to know hive0.6 whether can be released in next
>>>>>> week.
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> LiuLei
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to