[jira] [Commented] (IGNITE-4600) Apache Ignite Python Library
[ https://issues.apache.org/jira/browse/IGNITE-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927994#comment-16927994 ] Denis Magda commented on IGNITE-4600: - [~zyc], this ticket should be considered as outdated as long as Ignite already support Python: https://apacheignite.readme.io/docs/python-thin-client Please send an email to the dev list if you'd like to enhance the existing client anyhow. I'm closing this and all dependent tickets. > Apache Ignite Python Library > > > Key: IGNITE-4600 > URL: https://issues.apache.org/jira/browse/IGNITE-4600 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda >Priority: Major > Labels: gsoc2017 > > The goal of this ticket is to enable direct Python support for Apache Ignite > In-Memory Data Fabric. > This ticket is an umbrella ticket of basic functionality that should be > released first. > Python can be supported in several ways that have do be discussed on the dev > list: > - Use SWIG (http://www.swig.org) to generate Python API from Ignite.C++. > - Design and implement Python API from scratch talking to underlying JVM that > runs the node. > - Design and implement Python API from scratch talking to Ignite.C++ API that > talks to JVM on its turn. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-4600) Apache Ignite Python Library
[ https://issues.apache.org/jira/browse/IGNITE-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16920726#comment-16920726 ] Zhiyuan Chen commented on IGNITE-4600: -- Hi, I'm super interested in this topic, is there anyone currently working on it? > Apache Ignite Python Library > > > Key: IGNITE-4600 > URL: https://issues.apache.org/jira/browse/IGNITE-4600 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda >Priority: Major > Labels: gsoc2017 > > The goal of this ticket is to enable direct Python support for Apache Ignite > In-Memory Data Fabric. > This ticket is an umbrella ticket of basic functionality that should be > released first. > Python can be supported in several ways that have do be discussed on the dev > list: > - Use SWIG (http://www.swig.org) to generate Python API from Ignite.C++. > - Design and implement Python API from scratch talking to underlying JVM that > runs the node. > - Design and implement Python API from scratch talking to Ignite.C++ API that > talks to JVM on its turn. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (IGNITE-4600) Apache Ignite Python Library
[ https://issues.apache.org/jira/browse/IGNITE-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906597#comment-15906597 ] Madhawa Vidanapathirana commented on IGNITE-4600: - Hi [~dmagda], Is their any ongoing discussion already on how the Python API can be supported? (regarding 3 options given in description). If so, can you direct me to the discussion? > Apache Ignite Python Library > > > Key: IGNITE-4600 > URL: https://issues.apache.org/jira/browse/IGNITE-4600 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Denis Magda > Labels: gsoc2017 > > The goal of this ticket is to enable direct Python support for Apache Ignite > In-Memory Data Fabric. > This ticket is an umbrella ticket of basic functionality that should be > released first. > Python can be supported in several ways that have do be discussed on the dev > list: > - Use SWIG (http://www.swig.org) to generate Python API from Ignite.C++. > - Design and implement Python API from scratch talking to underlying JVM that > runs the node. > - Design and implement Python API from scratch talking to Ignite.C++ API that > talks to JVM on its turn. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4600) Apache Ignite Python Library
[ https://issues.apache.org/jira/browse/IGNITE-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906589#comment-15906589 ] Denis Magda commented on IGNITE-4600: - It depends on a number of folks who decide to work on this task. If you're the only one then the task will be fully yours. > Apache Ignite Python Library > > > Key: IGNITE-4600 > URL: https://issues.apache.org/jira/browse/IGNITE-4600 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Denis Magda > Labels: gsoc2017 > > The goal of this ticket is to enable direct Python support for Apache Ignite > In-Memory Data Fabric. > This ticket is an umbrella ticket of basic functionality that should be > released first. > Python can be supported in several ways that have do be discussed on the dev > list: > - Use SWIG (http://www.swig.org) to generate Python API from Ignite.C++. > - Design and implement Python API from scratch talking to underlying JVM that > runs the node. > - Design and implement Python API from scratch talking to Ignite.C++ API that > talks to JVM on its turn. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4600) Apache Ignite Python Library
[ https://issues.apache.org/jira/browse/IGNITE-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906448#comment-15906448 ] Madhawa Vidanapathirana commented on IGNITE-4600: - Hi, If this ticket is to be taken forward as my GSOC Project, should it cover all 4 sub tasks? > Apache Ignite Python Library > > > Key: IGNITE-4600 > URL: https://issues.apache.org/jira/browse/IGNITE-4600 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Denis Magda > Labels: gsoc2017 > > The goal of this ticket is to enable direct Python support for Apache Ignite > In-Memory Data Fabric. > This ticket is an umbrella ticket of basic functionality that should be > released first. > Python can be supported in several ways that have do be discussed on the dev > list: > - Use SWIG (http://www.swig.org) to generate Python API from Ignite.C++. > - Design and implement Python API from scratch talking to underlying JVM that > runs the node. > - Design and implement Python API from scratch talking to Ignite.C++ API that > talks to JVM on its turn. -- This message was sent by Atlassian JIRA (v6.3.15#6346)