Chris Stadler

For example, a self-loop: ``` Entities: employees Relationships: employees.manager_id -> employees.id ``` Or, a cycle involving multiple entities: ``` Entities: users roles Relationships users.role_id -> roles.id roles.creator_id -> users.id ```...

Currently a new dataframe is created with the secondary time variables, and then joined with dataframe for the new entity: https://github.com/Featuretools/featuretools/blob/4b6a5a4d38de94a64c08ad15b5b8cefa9954b6df/featuretools/entityset/entityset.py#L762-L776 This means that we are sometimes dropping columns and...

Possible breaking change with handling of `nil` conditions in 3.5.0

2

### Steps to reproduce In https://github.com/CanCanCommunity/cancancan/pull/653 the handling of `nil` with `has_many` relations was changed. Previously a rule like ```rb can :read, Document, authors: { user_id: nil } ``` caused...

This could be useful when there are multiple relationships between two entities. For example: ``` games.home_team_id -> teams.id games.away_team_id -> teams.id ``` Currently we disambiguate by using the `child_variable_id`, generating...

DFS does not build some features when there are multiple paths to an entity

1

DFS currently builds features for each entity only once. This is problematic because depending on which path is taken to an entity different features may be built. For example, the...

If we have a relationship `log.session_id -> sessions.id` and a feature `sessions: MEAN(log.value)` there is an implicit dependency on the features `sessions: id` and `log: session_id` – to calculate the...

Eventual Consistency

1

Does yas3fs do anything to deal with S3 only providing eventual consistency for read-after-write? For example, say a node receives an SNS notification that a file has changed and so...