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
In snowflake schema, How to set constraits if an intermediate table has no timestamp.
Hello, I am a getML user. I am trying to switch from featuretools to your tools. I appreciate this great job you did. But I encounter a problem:
suppose in some of datasets which is snowflake schema, T0 is target table, and there is a join path: T0->T1<-T2.
If T0, T1, T2 all have timestamp, that's OK, we can add constraints on join like
A more concrete example is in this schema, customers and calls have timestamp, but complaints does not. How can I add time constraints on customers and calls ?
But if T0 and T2 has timestamp, but T1 does not, I can not set timeconstraits althouth I would like to because T1 has no timestamp. It works fine on featuretools but does not work on getML. Do you plan to support such thing or are there any workwround?
The text was updated successfully, but these errors were encountered:
In snowflake schema, How to set constraits if an intermediate table has no timestamp.
Hello, I am a getML user. I am trying to switch from featuretools to your tools. I appreciate this great job you did. But I encounter a problem:
suppose in some of datasets which is snowflake schema, T0 is target table, and there is a join path: T0->T1<-T2.
If T0, T1, T2 all have timestamp, that's OK, we can add constraints on join like
A more concrete example is in this schema,

customers
andcalls
have timestamp, butcomplaints
does not. How can I add time constraints oncustomers
andcalls
?But if T0 and T2 has timestamp, but T1 does not, I can not set timeconstraits althouth I would like to because T1 has no timestamp. It works fine on featuretools but does not work on getML. Do you plan to support such thing or are there any workwround?
The text was updated successfully, but these errors were encountered: