Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -116,8 +116,8 @@ private SchemaShape.Column CheckInputsAndMakeColumn(
}
if (!col.ItemType.Equals(itemType))
{
throw _host.Except($"Column '{sources[i]}' has values of {col.ItemType}, " +
$"which is not the same as earlier observed type of {itemType}.");
throw _host.Except($"Concatenated columns should have the same type. Column '{sources[i]}' has values of {col.ItemType}, " +
$"but expected columns of type {itemType}.");

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Column '{sources[i]}' has type of {col.ItemType}, " +
$"but expected column type is {itemType}.

Will that be more clear?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I can remove the first sentence, if we think the user will know concatenated columns must have the same type.

@antoniovs1029 antoniovs1029 Oct 20, 2020

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the first sentence is all right. But maybe use the wording Frank suggested for the second one?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, first sentence is good, I mean change the second sentence little bit.


In reply to: 508886394 [](ancestors = 508886394)

}
varVector |= col.Kind == SchemaShape.Column.VectorKind.VariableVector;
isNormalized &= col.IsNormalized();
Expand Down