Hi,


We are evaluating the Carbondata for following alternative to Oracle –and
hit following issues when achieving this migration -



   1. Primary Key Indexes – how we can avoid duplicate records on Carbon?
   2. Secondary Indexes
   3. Constraints such as NULL, NOT NULL – how can we set this at column
   levels in carbon?
   4. Functions such as DECODE – what alternatives we have in Carbon to use
   these SQL functions?



Appreciate the response.



-- 
Regards,
Deepak

Reply via email to