Values greater than MaxFloat64 get evaluated as Binary type

EvaluateForIndex on values > greater than MaxFloat64 return binary types.

Repro steps with primary index
1. Create below document:

{ "f1": 7.7976931348623157e+467 }

2. CREATE PRIMARY INDEX `#primary` ON `default`

3. SELECT f1, meta().id FROM default WHERE f1 IS NOT NULL
[

{ "f1": "<binary (23 b)>", "id": "K2" }

]

In secondary index, EvaluateForIndex returns scalar as "<binary (23 b)>" with value Type as binary. Since binary is not a type of N1QL value that GSI understands this leads to an incomplete key in case of composite index.

What is the expected behavior in case of such numbers exceeding the range of Maxfloat64?