data_intersection sorted input error

dnrickner

• July 19, 2011 00:00

• Answered

Follow

I am receiving an error that says:

Data input B is not sorted in ascending order.

This seems to happen when we have either a null or empty string in the field we are specifying as a join key, and we are sorting by this join key. We need this to work with an empty string coming through. Is this a bug?

attached is my graph that demonstrates this. We are running on SQL Server 2008.

• testdata_intersection.grf

• 

  dnrickner

  • July 20, 2011 12:38

  0

  Comment actions Permalink

  I forgot to mention that I am using Clover 3.1 commercial version.
• 

  avackova

  • July 20, 2011 14:17

  0

  Comment actions Permalink

  Hello,
  unfortunately it's really bug.
  As a workaround, please add a Partitioner before the DataIntersection - it will send the records with null key to "flow B" directly, as you don't want to regard null as equals values.

  • testdata_intersection.grf
• 

  dnrickner

  • July 20, 2011 15:12

  0

  Comment actions Permalink

  Since it's a bug, could you post the bug tracking link?
• 

  avackova

  • July 21, 2011 06:25

  0

  Comment actions Permalink

  Ii is logged here. Please use guest/guest credentials for browsing.

Please sign in to leave a comment.