Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output Table Settings #54

Open
Squareys opened this issue Sep 22, 2016 · 3 comments
Open

Output Table Settings #54

Squareys opened this issue Sep 22, 2016 · 3 comments

Comments

@Squareys
Copy link
Contributor

For different types of nodes we require different output settings:

Node Type Replace Append New Table
0:n (Source) x
1:1 (No Multi Columns) x x x
1:1 (Mutli Column In) x x
1:1 (Mutli Column Out) x x x
1:1 (Mutli Column In & Out) x x
1:n x
n:1 x
n:m x
n:0 (Sink) x

@dietzc Did I miss something? :)

@dietzc
Copy link
Member

dietzc commented Sep 22, 2016

I think we have to consider the following use-cases:

  • 1-Row:N-Rows, 1-Column:L-Columns: Replace, Append, New Table.
  • 1-Row:N-Rows, M-Column:L-Columns: Append, New Table.
  • K-Row:N-Rows, L-Column:1-Columns: New Table.
  • Source: New Table.
  • Sink: -

Did I miss something?

@imagejan
Copy link

What about a Replace first option or some such (cf. Column Merger node), or a choice of which column to replace (cf. Image Calculator) for multi-column inputs?

For the K-Rows:N-Rows case above (I'm thinking of use cases similar to GroupBy), it would also be useful to have an option to append some information from the input rows, to avoid the need of a subsequent joiner. But this will probably have to be taken care of by the script developer, as it's not generalizable, right?

@dietzc
Copy link
Member

dietzc commented Sep 22, 2016

What about a Replace first option or some such (cf. Column Merger node), or a choice of which column to replace (cf. Image Calculator) for multi-column inputs?

I like the idea of being able to determine the column to be replaced.

For the K-Rows:N-Rows case above (I'm thinking of use cases similar to GroupBy), it would also be useful to have an option to append some information from the input rows, to avoid the need of a subsequent joiner. But this will probably have to be taken care of by the script developer, as it's not generalizable, right?

I was thinking about this a lot and I didn't find a nice solution at all, because you don't know which input row should be appended to which output-row (as the resulting output-row may depend on many input rows).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants