From d53ccf7ead5d04b700ce39ef7af73306a2e08d46 Mon Sep 17 00:00:00 2001
From: pdeva <prashant.deva@gmail.com>
Date: Tue, 16 Sep 2014 15:56:15 -0700
Subject: [PATCH] segment metadata result explained better

---
 docs/content/SegmentMetadataQuery.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/docs/content/SegmentMetadataQuery.md b/docs/content/SegmentMetadataQuery.md
index ddc5910b618..c69cd33677c 100644
--- a/docs/content/SegmentMetadataQuery.md
+++ b/docs/content/SegmentMetadataQuery.md
@@ -46,6 +46,12 @@ The format of the result is:
 } ]
 ```
 
+Dimension columns will have type `STRING`.  
+Metric columns will have type `FLOAT`.  
+Timestamp column will have type `LONG`.
+
+Only columns which are dimensions (ie, have type `STRING`) will have any cardinality. Rest of the columns (timestamp and metric columns) will show cardinality as `null`.
+
 ### toInclude
 
 There are 3 types of toInclude objects.
@@ -72,4 +78,4 @@ The grammar is as follows:
 
 ``` json
 "toInclude": { "type": "list", "columns": [<string list of column names>]}
-```
\ No newline at end of file
+```