Hi David Thanks for the reply. As per the earlier implementation, both date and timestamp data types were treated as Direct Dictionary type and for both the keys were generated using the DirectDictionaryKeyGenerator. Now the behavior is changed and timestamp is treated as no dictionary by default. I am not clear why this behavior is changed. Can you please clarify my doubt?
On Thu, Mar 22, 2018 at 9:06 AM, David CaiQiang <[email protected]> wrote: > Hi Jatin, Timestamp column is non-dictionary by default. After adding the > Timestamp column to the table property 'dictionary_include', it will have > the same encoding list. > > > > > > ----- > Best Regards > David Cai > -- > Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556. > n5.nabble.com/ > -- Thanks & Regards Jatin
