You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by "Fu Yi (BT - AI, Analytics & Data Domain)" <yi...@hm.com> on 2022/03/24 08:54:12 UTC
Beam VertexAI feature store IO
Hi there:
As far as I know, there is no built-in IO for Vertex AI feature store yet? Is there any plan to add it by the community or is there any work been doing right now?
Best regards,
Yi
The information contained in this e-mail message may be privileged, confidential, and protected from disclosure. Any unauthorized use, printing, copying, disclosure or dissemination of this communication may be subject to legal restriction or sanction. If you think that you have received this e-mail message in error, please reply to the sender and delete this message from your computer.
General Information
Re: Beam VertexAI feature store IO
Posted by Kerry Donny-Clark <ke...@google.com>.
Hi Alexey,
The Vertex AI team is planning this work, but there isn't a design yet. I'd
be happy to discuss if you have plans to work on this, I think it would be
great if we can design the IO earlier.
Kerry
On Fri, Mar 25, 2022 at 1:59 PM Alexey Romanenko <ar...@gmail.com>
wrote:
> Kerry,
>
> Could you share any details on this plan? I didn’t find any jira nor
> design doc for that.
> Thanks
>
> —
> Alexey
>
> On 24 Mar 2022, at 17:12, Kerry Donny-Clark <ke...@google.com> wrote:
>
> Hello,
> A Vertex AI feature store IO is planned for this summer, but we would
> welcome a contribution earlier if you'd like to help.
> Kerry
>
> On Thu, Mar 24, 2022 at 12:03 PM Fu Yi (BT - AI, Analytics & Data Domain) <
> yi.fu@hm.com> wrote:
>
>> Hi there:
>>
>> As far as I know, there is no built-in IO for Vertex AI feature store
>> yet? Is there any plan to add it by the community or is there any work been
>> doing right now?
>>
>> Best regards,
>> Yi
>>
>> The information contained in this e-mail message may be privileged,
>> confidential, and protected from disclosure. Any unauthorized use,
>> printing, copying, disclosure or dissemination of this communication may be
>> subject to legal restriction or sanction. If you think that you have
>> received this e-mail message in error, please reply to the sender and
>> delete this message from your computer.
>>
>> General Information
>>
>
>
Re: Beam VertexAI feature store IO
Posted by Alexey Romanenko <ar...@gmail.com>.
Kerry,
Could you share any details on this plan? I didn’t find any jira nor design doc for that.
Thanks
—
Alexey
> On 24 Mar 2022, at 17:12, Kerry Donny-Clark <ke...@google.com> wrote:
>
> Hello,
> A Vertex AI feature store IO is planned for this summer, but we would welcome a contribution earlier if you'd like to help.
> Kerry
>
> On Thu, Mar 24, 2022 at 12:03 PM Fu Yi (BT - AI, Analytics & Data Domain) <yi.fu@hm.com <ma...@hm.com>> wrote:
> Hi there:
>
> As far as I know, there is no built-in IO for Vertex AI feature store yet? Is there any plan to add it by the community or is there any work been doing right now?
>
> Best regards,
> Yi
>
> The information contained in this e-mail message may be privileged, confidential, and protected from disclosure. Any unauthorized use, printing, copying, disclosure or dissemination of this communication may be subject to legal restriction or sanction. If you think that you have received this e-mail message in error, please reply to the sender and delete this message from your computer.
>
>
> General Information
>
Re: Beam VertexAI feature store IO
Posted by Kerry Donny-Clark <ke...@google.com>.
Hello,
A Vertex AI feature store IO is planned for this summer, but we would
welcome a contribution earlier if you'd like to help.
Kerry
On Thu, Mar 24, 2022 at 12:03 PM Fu Yi (BT - AI, Analytics & Data Domain) <
yi.fu@hm.com> wrote:
> Hi there:
>
> As far as I know, there is no built-in IO for Vertex AI feature store yet?
> Is there any plan to add it by the community or is there any work been
> doing right now?
>
> Best regards,
> Yi
>
> The information contained in this e-mail message may be privileged,
> confidential, and protected from disclosure. Any unauthorized use,
> printing, copying, disclosure or dissemination of this communication may be
> subject to legal restriction or sanction. If you think that you have
> received this e-mail message in error, please reply to the sender and
> delete this message from your computer.
>
> General Information
>