The assignment behavior of DGLGraph.dstdata is wrong in some cases

[yfismine]

The assignment behavior of DGLGraph.dstdata is wrong in some cases

[frozenbugs]

What's your use case of using to_block()?

[yfismine]

What's your use case of using to_block()?

DGLGraph

[frozenbugs]

to_block is to create a bipartite-structured block for message passing. It is more an internal util method than public api of dgl, we expose it just in case users want to experiment with it. Can you be more specific about why you need to use to_block to create a bipartite-structured block? Can DGLGraph fit your need?

[yfismine]

to_block is to create a bipartite-structured block for message passing. It is more an internal util method than public api of dgl, we expose it just in case users want to experiment with it. Can you be more specific about why you need to use to_block to create a bipartite-structured block? Can DGLGraph fit your need?

It is found that the assignment behavior here is normal if to_block is not used. I encountered this problem when I used dist dgl for neighbor sampling and found that the generated block has no attributes. I need to pull data through DistGraph in a way like "batch _ labels = g. ndata ["labels "] [seeds]. long (). To (device)". I hope to unify the training codes of stand-alone and distributed. I re-implement the sampler_block of neighborSampler and assign attributes to the block in it.

[github-actions]

This issue has been automatically marked as stale due to lack of activity. It will be closed if no further activity occurs. Thank you