You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes going through a whole array is not needed. You have the types of the subsets of the array and you just want to get a compatible data type for all subsets.
A common scenario when assembling horrible csvs is that the same column might be inferred as different types in different csvs. For example, (float <-- int). Worst case is to 'fall back' to string.
The text was updated successfully, but these errors were encountered:
Hey Majid, great observation. Although it’s not exactly what you’re looking for we have a performance enhancement implementation leveraging this fact under ‘visions.type sets.typeset’ called ‘traverse_graph_with_sampled_series’ that you can invoke directly for a quick speed up win.
More broadly, if instead of the ‘detect_type’ method you simply use ‘detect’ (and infer counterparts) you can pull the full inference path which consists of a list of nodes from root to final. You can then find the intersections between columns across your discrete data sets to determine a best representation.
On Tue, Dec 22 2020 at 12:37 PM, Majid alDosari < ***@***.*** > wrote:
Sometimes going through a whole array is not needed. You have subsets of
the array and you just want to get a compatible data type for all subsets.
A common scenario when assembling horrible csvs is that the same column
might be inferred as different types in different csvs. For example,
(float <-- int). Worst case is to 'fall back' to string.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (
#157 ) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AB3MV54GPBNRRD4SHHRGN4TSWDKMDANCNFSM4VF5XCUA
).
Sometimes going through a whole array is not needed. You have the types of the subsets of the array and you just want to get a compatible data type for all subsets.
A common scenario when assembling horrible csvs is that the same column might be inferred as different types in different csvs. For example, (float <-- int). Worst case is to 'fall back' to string.
The text was updated successfully, but these errors were encountered: