Skip to main content
Solved

Summary Annotation - size limited for transformers?


joshuadamron
Contributor
Forum|alt.badge.img+7

Howdy!

I have a question about "Summary Annotation", when used with transformers like the AttributeManager or AttributeRenamer it does not expose all of the attributes. Example of the transformer issue: Using "Summary Annotation" with an AttributeManager transformer, the list/table of "Attribute Actions" that is shown is limited to 20 (seemingly random) attributes/rows. At the bottom of the annotation list/table it states "41 more row(s)". Is this just a default setting? Is there a way to get it to show me the other 41 rows? Compared with a Reader/Writer: However it appears that Summary Annotation exposes all of the data when used with Readers/Writers. I noticed that when I use Summary Annotation for a transformer like a SQL Writer, there seems to be no limit to how long the list/table of fields/attributes/rows that can be displayed.

 

 

Any help understanding this limitation and/or a work around is appreciated.

Best answer by stalknecht

The current behavior is as you describe. If you want more flexibility you can post an idea on this forum. I'll suggest not to use these large annotation lists. If you want it for documentation then it's better to feed the workspace to a workspace-reader and generate the documentation as you want it to be.

View original
Did this help you find an answer to your question?

2 replies

stalknecht
Contributor
Forum|alt.badge.img+19
  • Contributor
  • Best Answer
  • August 16, 2018

The current behavior is as you describe. If you want more flexibility you can post an idea on this forum. I'll suggest not to use these large annotation lists. If you want it for documentation then it's better to feed the workspace to a workspace-reader and generate the documentation as you want it to be.


joshuadamron
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • August 21, 2018
stalknecht wrote:

The current behavior is as you describe. If you want more flexibility you can post an idea on this forum. I'll suggest not to use these large annotation lists. If you want it for documentation then it's better to feed the workspace to a workspace-reader and generate the documentation as you want it to be.

Thank you for the confirmation!

 

 

I assume that by "feed the workspace to a workspace-reader" you mean to connect a reader immediately after the transformer (like AttributeManager in my example) to get the full "Summary Annotation" for documentation.

 

 

That while that won't output any expressions performed in the Attribute Value column, it will get me a lot closer for the purposes of documenting what the transformer is doing.

 

 

Thank you again for the help.

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings