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
We know that using anything other than valid Java identifier names can cause problems with ExpressionFunction & ExpressionFilter, due to limitations in what the Janino compiler can infer from a text snippet. In addition, names shouldn't start with an uppercase letter.
So it would be nice to have a way to generate warnings when problematic field names were used. This ideally would be something you could control via a parameter passed to FlowConnector.connect(), but this would be a start.
The text was updated successfully, but these errors were encountered:
So to clarify, I'm thinking of adding code to the step naming support already in Cascading utils. Though I could create an abstract BaseConnector that provides this support, and would be returned by HadoopPlatform/LocalPlatform.
We know that using anything other than valid Java identifier names can cause problems with ExpressionFunction & ExpressionFilter, due to limitations in what the Janino compiler can infer from a text snippet. In addition, names shouldn't start with an uppercase letter.
So it would be nice to have a way to generate warnings when problematic field names were used. This ideally would be something you could control via a parameter passed to FlowConnector.connect(), but this would be a start.
The text was updated successfully, but these errors were encountered: