Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

datatype and encoding should not be case sensitive #64

Open
csliuyb opened this issue Aug 16, 2017 · 0 comments
Open

datatype and encoding should not be case sensitive #64

csliuyb opened this issue Aug 16, 2017 · 0 comments

Comments

@csliuyb
Copy link

csliuyb commented Aug 16, 2017

I can type int32 or INT32 and rle or RLE, which will make developers feel more confortable.

qq 20170816203033

IoTDB> create timeseries root.vehicle.d0.s1
statement error: Statement format is not right:parsing error,statement: create timeseries root.vehicle.d0.s1 .message:line 1:36 mismatched input '' expecting WITH near 's1'. Please refer to SQL document and check if there is any keyword conflict.
IoTDB> create timeseries root.vehicle.d0.s1 with datatype=int32 encoding=rle
statement error: Statement format is not right:parsing error,statement: create timeseries root.vehicle.d0.s1 with datatype=int32 encoding=rle .message:line 1:57 missing , at 'encoding' near ''. Please refer to SQL document and check if there is any keyword conflict.
IoTDB> create timeseries root.vehicle.d0.s1 with datatype=int32,encoding=rle
statement error: data type int32 not support
IoTDB> create timeseries root.vehicle.d0.s1 with datatype=INT32,encoding=rle
statement error: encoding rle is not support
IoTDB> create timeseries root.vehicle.d0.s1 with datatype=INT32,encoding=RLE
execute successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant