[COMPASS-2185] Binary type handled poorly Created: 10/Oct/17  Updated: 29/Oct/23  Resolved: 11/Dec/18

Status: Closed
Project: Compass
Component/s: Compass, Query Bar
Affects Version/s: 1.10.0-dev
Fix Version/s: 1.16.0

Type: Bug Priority: Major - P3
Reporter: Andrew Ryder (Inactive) Assignee: Durran Jordan
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2018-12-11 at 15.57.29.png     PNG File compass-binary.PNG    
Issue Links:
Related
is related to COMPASS-1083 LUUID/NUUID/BinData support for filters Closed
Epic Link: COMPASS-2232
Sprint: Iteration Takaioko

 Description   

Compass doesn't handle the BinData type cleanly in various ways. As follows:

  1. Multiple BinData with the same value but different subtypes cause Compass to treat them as the same document (see screenshot): "Displaying documents 1-20" but only 1 document is shown.
  2. The subtype is not shown in any location.
  3. Nothing I typed in the filter bar ever matched – suggested format (and the 'green' allowed format) was Binary('xxxx') but no value I gave ever produced results.
  4. The shell type is BinData (rather than Binary) and would be preferred for copy/paste purposes.
  5. The presence of a document with a BinData value of subtype 2 causes Compass to throw an error instead of showing the documents (or doing schema analysis).


 Comments   
Comment by Durran Jordan [ 11/Dec/18 ]

The rendering issue is fixed in Compass 1.16 stable.

Comment by Brian Blevins [ 11/Oct/17 ]

https://app.intercom.io/a/apps/p57suhg7/respond/inbox/search/conversations/10536819394

Comment by Brian Blevins [ 11/Oct/17 ]

https://app.intercom.io/a/apps/p57suhg7/respond/inbox/search/conversations/11418851941

Comment by Brian Blevins [ 11/Oct/17 ]

Intercom.io conversation concerning inability to search on binary fields:
https://app.intercom.io/a/apps/p57suhg7/respond/inbox/1486670/conversations/12159800172

Generated at Wed Feb 07 22:29:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.