Richard Whitcomb
Richard Whitcomb
Seeing this also. I would be open to taking a shot at a PR if the best option was pointed out. Looks like you can't simply changing the code generation...
We are having the same issue trying Amundsen internally. Also using ambassador with the helm chat provided.
We already have something close to this. Is the idea around instead of being limited to just a String we could give a list of Strings etc? How would you...
I looked at adding sumOption but couldn't think of a way to make it more efficient without a lot of complexity and not sure if it is entirely worth it....
Wonder if there is a way to pair a TF Estimator with equivalent JVM prediction code. So if you want to use say a pre-canned logistic regression estimator in normal...
Seems like most of those algorithms could be written in terms of the Graph structure. The nice thing of this new abstraction is working natively with vertices and minimizing data...
Added an example of doing cosine similarity with the Graph class. The intersection methods clearly need unit tests but wanted to show an example.
Decided to simply this PR a bit and removed the example vertex similarity code and the neighbor intersection. I can do a followup PR adding the intersection logic back in....
Also for now I think it might be helpful to keep collectNeighborIds separate from collectNeighbor. Worried mostly about the memory overhead of first collecting the vertices with the attributes then...
Modified scald.rb also here. It look kind of broken if you gave it a jar. Now if you pass it a jar and it exists on disk it will use...