Toben
My feedback
20 results found
-
2 votes
Toben supported this idea ·
-
40 votes
Thank you all for your feedback!
We hear you loud and clear and are working on exposing these details in the next quarter.
Toben supported this idea ·
-
17 votes
Toben supported this idea ·
-
10 votes
Toben supported this idea ·
-
14 votes
Toben supported this idea ·
-
47 votes
Toben supported this idea ·
-
66 votes
Toben supported this idea ·
-
30 votes
Toben supported this idea ·
-
8 votes
Toben supported this idea ·
-
3 votes
Toben supported this idea ·
-
382 votes
Toben supported this idea ·
-
27 votes
Toben supported this idea ·
-
11 votes
Toben supported this idea ·
-
9 votes
An error occurred while saving the comment Toben supported this idea ·
-
170 votes
Toben supported this idea ·
-
2 votes
-
13 votes
Toben supported this idea ·
-
2 votes
Toben supported this idea ·
-
14 votes
Toben supported this idea ·
-
6 votes
Toben supported this idea ·
Honestly, probably the steepest learning curve for anyone implementing Search is understanding the grimy details of how analyzers break up various types of inputs. It would be incredibly empowering to have this functionality built into the Atlas Search UI somewhere, presumably in the Visual Index Editor. Also, I'm sure it would serve to deflect a lot of cases as customers would know exactly what there data looks like for purposes of crafting a Search query.