Github user andralungu commented on the pull request:
https://github.com/apache/flink/pull/847#issuecomment-121039562
Yes, but then you would have the following methods: `types`,
`typesNoEdgeValue`, `typesNoVertexValue` and again `types`. So, even if it's
not 100% needed I'd try to keep it consistent. We could also make it more
graph-oriented (the name `types` was generic). The following is just an example:
1). keyType(K)
2). keyAndVertexTypes(K, VV)
3). keyAndEdgeTypes(K, EV)
4). keyVertexAndEdgeTypes(K, VV, EV)
With a nice documentation, I think I'd understand what these are for :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
