HEXPIRE key seconds [NX | XX | GT | LT] FIELDS numfields field [field ...], it's totally useless. it's client CLI or client SDK's responsibility to get the whole HEXPIRE command, parse it, and send fields as an array to the server side.
Comment From: sundb
not sure i can follow you, do you mean HEXPIRE key seconds [NX | XX | GT | LT] FIELDS field [field ...]?
so how do we know the boundaries of the FIELDS? You might want to say read from FIELDS to the end, but then we won't be able to extend it in the future and add more parameters to it.
Comment From: pfwang80s
You might want to say read from FIELDS to the end, but then we won't be able to extend it in the future and add more parameters to it.
just introduce another key word like FIELDS or simply let the newly added parameters be front of FIELDS
Comment From: pfwang80s
something like: HEXPIRE key seconds [NX | XX | GT | LT] FIELDS field [field ...] ANOTHER x1 x2 x3 or HEXPIRE key seconds [NX | XX | GT | LT] [ANOTHER1 | ANOTHER2] [ANOTHER3 | ANOTHER4] FIELDS field [field ...]
Just as database normalization and duplicated code are unacceptable, so too is providing redundant information in hits