See screenshot below.Īnd from the "type" dropdown, there is no option for date or timestamp.
Mongodb metabase update#
(So that's on us to change/update.)īut here's my primary question based on the above, from the "Data Model" page when I attempt to update my field "types" for a specific collection, shouldn't the options for date or timestamp still be present?įor the fields where Metabase does display date within the visual query-builder, the Metabase auto-assigned type in the Data Model is always "select a special type". However, our bson data types are all set to object. At a quick glance, the "misses" do seem correlated with a high ratio of null-to-notnull values within the respective field. But wanted to bring up the missing type options (below) in case there's something else going on regarding mongo.Īcross my mongodb collection, it seems Metabase is hit-or-miss within the visual query-builder when it comes to correctly determining the date or timestamp type of any given field. Regardless I'll get to work on updating our bson to specify data types (and maybe this is the core issue). Attempting to build a native query does not resolve issue. Furthermore, I cannot manually set the date or timestamp type from the "Data Model" admin page. "demand_created_datetime": ISODate("T02:36:56.713Z")įor my mongodb data, I'm trying to display a table of "count over time" results but running into issues where fields are not recognized as a date type, which blocks correct table display possibility (uses "row chart" instead). I'd also be okay with being able to specify date type in the data Model on admin view to resolve this. What is type determination based on? Random sampling? Majority values? Why is this field not being recognised as a date? the other two I can think of it that this one probably has more records set as null than the others. The only difference between this column Vs. This leads to obvious problem for the third (filtering, grouping, how it looks in a table). Metabase does great at determining the type of 2 but not the third.
I have 3 datetime fields in MongoDB with values set as either $date BSON Mongo type or null.
0 kommentar(er)
