Hi, Raj!
MergeTree primary key can be an arbitrary tuple (presence of the date column is not mandatory, it just makes sense in the examples). Primary key index affects the physical structure of the table (the table consists of several parts each of which is sorted by primary key), thus there can be only one such index.
Most of the times one index is enough but there are legitimate cases where several indexes are desirable - e.g. in an ad serving platform there are advertisers and ad network sites where the ads are displayed. To be able to efficiently generate a report both for an advertiser or an ad network site you will need two indexes. One possible way to circumvent this limitation is to duplicate the data in two tables.