On Mon, Nov 12, 2018 at 10:48 AM Amar Tumballi wrote:
>
>
> On Mon, Nov 12, 2018 at 10:39 AM Vijay Bellur wrote:
>
>>
>>
>> On Sun, Nov 11, 2018 at 8:25 PM Raghavendra Gowdappa
>> wrote:
>>
>>>
>>>
>>> On Sun, Nov 11, 2018 at 11:41 PM Vijay Bellur
>>> wrote:
>>>
On Mon, Nov 5,
On Mon, Nov 12, 2018 at 10:39 AM Vijay Bellur wrote:
>
>
> On Sun, Nov 11, 2018 at 8:25 PM Raghavendra Gowdappa
> wrote:
>
>>
>>
>> On Sun, Nov 11, 2018 at 11:41 PM Vijay Bellur wrote:
>>
>>>
>>>
>>> On Mon, Nov 5, 2018 at 8:31 PM Raghavendra Gowdappa
>>> wrote:
>>>
On Tue, Nov
On Sun, Nov 11, 2018 at 8:25 PM Raghavendra Gowdappa
wrote:
>
>
> On Sun, Nov 11, 2018 at 11:41 PM Vijay Bellur wrote:
>
>>
>>
>> On Mon, Nov 5, 2018 at 8:31 PM Raghavendra Gowdappa
>> wrote:
>>
>>>
>>>
>>> On Tue, Nov 6, 2018 at 9:58 AM Vijay Bellur wrote:
>>>
On Mon, Nov 5,
On Mon, Nov 5, 2018 at 8:31 PM Raghavendra Gowdappa
wrote:
>
>
> On Tue, Nov 6, 2018 at 9:58 AM Vijay Bellur wrote:
>
>>
>>
>> On Mon, Nov 5, 2018 at 7:56 PM Raghavendra Gowdappa
>> wrote:
>>
>>> All,
>>>
>>> There is a patch [1] from Kotresh, which makes ctime generator as
>>> default in
On Tue, Nov 6, 2018 at 9:58 AM Vijay Bellur wrote:
>
>
> On Mon, Nov 5, 2018 at 7:56 PM Raghavendra Gowdappa
> wrote:
>
>> All,
>>
>> There is a patch [1] from Kotresh, which makes ctime generator as default
>> in stack. Currently ctime generator is being recommended only for usecases
>> where
On Mon, Nov 5, 2018 at 7:56 PM Raghavendra Gowdappa
wrote:
> All,
>
> There is a patch [1] from Kotresh, which makes ctime generator as default
> in stack. Currently ctime generator is being recommended only for usecases
> where ctime is important (like for Elasticsearch). However, a reliable
>