Open diaohancai opened 9 months ago
ComputerOptions.INPUT_FILTER_CLASS default value is DefaultInputFilter. org.apache.hugegraph.computer.core.input.filter.DefaultInputFilter
ComputerOptions.INPUT_FILTER_CLASS
DefaultInputFilter
org.apache.hugegraph.computer.core.input.filter.DefaultInputFilter
public class DefaultInputFilter implements InputFilter { @Override public Vertex filter(Vertex vertex) { vertex.properties().clear(); return vertex; } @Override public Edge filter(Edge edge) { edge.properties().clear(); return edge; } }
Load all properties first, then clear.
Could we specify some properties when loading vertices or edges? May could improve performance. Just like mysql:
select a, b, c
instead of
select *
org.apache.hugegraph.computer.core.input.hg.HugeVertexFetcher
@Override public Iterator<Vertex> fetch(InputSplit split) { Shard shard = toShard(split); return this.client().traverser().iteratorVertices(shard, this.pageSize()); }
But it seems that the traverser api does not yet support specifying some properties to load vertices or edges on the server side.
Feature Description (功能描述)
ComputerOptions.INPUT_FILTER_CLASS
default value isDefaultInputFilter
.org.apache.hugegraph.computer.core.input.filter.DefaultInputFilter
Load all properties first, then clear.
Could we specify some properties when loading vertices or edges? May could improve performance. Just like mysql:
instead of
org.apache.hugegraph.computer.core.input.hg.HugeVertexFetcher
But it seems that the traverser api does not yet support specifying some properties to load vertices or edges on the server side.