Mailing-List: contact user-help@flink.apache.org; run by ezmlm
Precedence: bulk
Subject: Re: VertexUpdateFunction
To: user@flink.apache.org
References: <20170529092815.Horde.RboFL3-0rrZWb9uJHuSQ-Xs@mail.uni-leipzig.de>
From: Martin Junghanns <m.junghanns@mailbox.org>
Message-ID: <bd7e86b6-c69f-4da7-3c9a-0d65c0f6813a@mailbox.org>
Date: Mon, 29 May 2017 19:38:20 +0200
MIME-Version: 1.0
In-Reply-To: <20170529092815.Horde.RboFL3-0rrZWb9uJHuSQ-Xs@mail.uni-leipzig.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
archived-at: Mon, 29 May 2017 17:38:35 -0000

Hi Ali :)

You could compute the degrees beforehand (e.g. using the 
Graph.[in|out|get]degrees()) methods and use the resulting dataset as a 
new vertex dataset. You can now run your vertex-centric computation and 
access the degrees as vertex value.

Cheers,

Martin


On 29.05.2017 09:28, rostami@informatik.uni-leipzig.de wrote:
> Hi,
>
> I want to write an iterative algorithm using Gelly (spargel), like:
>
> https://ci.apache.org/projects/flink/flink-docs-release-0.8/spargel_guide.html 
>
>
> My question is how I can access the actual vertex information like the 
> vertex degree (in- or outdegree)
> under the subclass of VertexUpdateFunction. A way is maybe to send an 
> instance of graph to the constructor.
> However, getting the degree for a vertex in each instance of this 
> subclass would be really inefficient.
>
> Thanks,
> Ali
>