[jira] [Commented] (IGNITE-9974) Drop Hadoop assemblies
[ https://issues.apache.org/jira/browse/IGNITE-9974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949796#comment-16949796 ] Denis A. Magda commented on IGNITE-9974: [~vveider], I'm fully for adding this to 2.8 as long as IGFS and Hadoop Accelerator are to be removed with this release. > Drop Hadoop assemblies > -- > > Key: IGNITE-9974 > URL: https://issues.apache.org/jira/browse/IGNITE-9974 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > > After dropping Hadoop binaries from release delivery (see IGNITE-9953) it is > required to drop assemblies and corresponding files / profiles if exist. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9974) Drop Hadoop assemblies
[ https://issues.apache.org/jira/browse/IGNITE-9974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-9974: --- Fix Version/s: 2.8 > Drop Hadoop assemblies > -- > > Key: IGNITE-9974 > URL: https://issues.apache.org/jira/browse/IGNITE-9974 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.8 > > > After dropping Hadoop binaries from release delivery (see IGNITE-9953) it is > required to drop assemblies and corresponding files / profiles if exist. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-6241) Integrate with Kubernetes StatefulSet to support Ignite Persistence
[ https://issues.apache.org/jira/browse/IGNITE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-6241. -- > Integrate with Kubernetes StatefulSet to support Ignite Persistence > --- > > Key: IGNITE-6241 > URL: https://issues.apache.org/jira/browse/IGNITE-6241 > Project: Ignite > Issue Type: New Feature >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Critical > Fix For: 2.9 > > Attachments: grid.yaml, namespace.yaml, pds-config.xml, role.yaml, > rolebind.yaml, sa.yaml, service.yaml, tutorial_k8s.txt > > > Ignite Kubernetes integration has to support StatefulSet which enables Ignite > Persistence usage in Kubernetes deployments. More details are here: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Persistence-on-Kubernetes-td16396.html > See how it's done for Cassandra and MongoDB: > * https://kubernetes.io/docs/tutorials/stateful-application/cassandra/ > * https://kubernetes.io/docs/tutorials/stateless-application/guestbook/ > We can reach out K8 folks and ask to add a prepared Ignite tutorial to the > list. > Good reading on the stateful set: > https://lenadroid.github.io/posts/stateful-sets-kubernetes-azure.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-6241) Integrate with Kubernetes StatefulSet to support Ignite Persistence
[ https://issues.apache.org/jira/browse/IGNITE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949795#comment-16949795 ] Denis A. Magda commented on IGNITE-6241: Closing this ticket, the task was solved and the StatefulState usage was documented in our K8 section: https://apacheignite.readme.io/docs/kubernetes-deployment > Integrate with Kubernetes StatefulSet to support Ignite Persistence > --- > > Key: IGNITE-6241 > URL: https://issues.apache.org/jira/browse/IGNITE-6241 > Project: Ignite > Issue Type: New Feature >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Critical > Fix For: 2.9 > > Attachments: grid.yaml, namespace.yaml, pds-config.xml, role.yaml, > rolebind.yaml, sa.yaml, service.yaml, tutorial_k8s.txt > > > Ignite Kubernetes integration has to support StatefulSet which enables Ignite > Persistence usage in Kubernetes deployments. More details are here: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Persistence-on-Kubernetes-td16396.html > See how it's done for Cassandra and MongoDB: > * https://kubernetes.io/docs/tutorials/stateful-application/cassandra/ > * https://kubernetes.io/docs/tutorials/stateless-application/guestbook/ > We can reach out K8 folks and ask to add a prepared Ignite tutorial to the > list. > Good reading on the stateful set: > https://lenadroid.github.io/posts/stateful-sets-kubernetes-azure.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-6241) Integrate with Kubernetes StatefulSet to support Ignite Persistence
[ https://issues.apache.org/jira/browse/IGNITE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-6241. Resolution: Fixed > Integrate with Kubernetes StatefulSet to support Ignite Persistence > --- > > Key: IGNITE-6241 > URL: https://issues.apache.org/jira/browse/IGNITE-6241 > Project: Ignite > Issue Type: New Feature >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Critical > Fix For: 2.9 > > Attachments: grid.yaml, namespace.yaml, pds-config.xml, role.yaml, > rolebind.yaml, sa.yaml, service.yaml, tutorial_k8s.txt > > > Ignite Kubernetes integration has to support StatefulSet which enables Ignite > Persistence usage in Kubernetes deployments. More details are here: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Persistence-on-Kubernetes-td16396.html > See how it's done for Cassandra and MongoDB: > * https://kubernetes.io/docs/tutorials/stateful-application/cassandra/ > * https://kubernetes.io/docs/tutorials/stateless-application/guestbook/ > We can reach out K8 folks and ask to add a prepared Ignite tutorial to the > list. > Good reading on the stateful set: > https://lenadroid.github.io/posts/stateful-sets-kubernetes-azure.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-3690) Log Message Glossary
[ https://issues.apache.org/jira/browse/IGNITE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949794#comment-16949794 ] Denis A. Magda commented on IGNITE-3690: [~mmuzaf], that's right. I removed a target version at all. > Log Message Glossary > > > Key: IGNITE-3690 > URL: https://issues.apache.org/jira/browse/IGNITE-3690 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 1.4 >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Minor > > It's time for Ignite to create a page which lists ALL the log messages, their > common causes and potential solutions. > Probably it makes sense to assign an unique ID for the most well-know errors > so that a user is able to look up an error in the glossary quicker. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-3690) Log Message Glossary
[ https://issues.apache.org/jira/browse/IGNITE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-3690: --- Fix Version/s: (was: 2.8) > Log Message Glossary > > > Key: IGNITE-3690 > URL: https://issues.apache.org/jira/browse/IGNITE-3690 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 1.4 >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Minor > > It's time for Ignite to create a page which lists ALL the log messages, their > common causes and potential solutions. > Probably it makes sense to assign an unique ID for the most well-know errors > so that a user is able to look up an error in the glossary quicker. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12281) Data search from Ignite Cache value object
[ https://issues.apache.org/jira/browse/IGNITE-12281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949793#comment-16949793 ] Denis A. Magda commented on IGNITE-12281: - Agree with Ivan, please address this question to the user list. Closing this ticket. > Data search from Ignite Cache value object > -- > > Key: IGNITE-12281 > URL: https://issues.apache.org/jira/browse/IGNITE-12281 > Project: Ignite > Issue Type: Wish >Reporter: ROHIT SANGWAN >Priority: Major > > Hi Team, > > I am solution for data look up from Ignite cache value. I found multiple > operation where I can use key to get the value. But I have a use case where I > want to apply search on few attributes of value on a certain cache. I tried > scan query but its very costly operation. Please help me to find a effective > solution. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12281) Data search from Ignite Cache value object
[ https://issues.apache.org/jira/browse/IGNITE-12281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-12281. --- > Data search from Ignite Cache value object > -- > > Key: IGNITE-12281 > URL: https://issues.apache.org/jira/browse/IGNITE-12281 > Project: Ignite > Issue Type: Wish >Reporter: ROHIT SANGWAN >Priority: Major > > Hi Team, > > I am solution for data look up from Ignite cache value. I found multiple > operation where I can use key to get the value. But I have a use case where I > want to apply search on few attributes of value on a certain cache. I tried > scan query but its very costly operation. Please help me to find a effective > solution. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12281) Data search from Ignite Cache value object
[ https://issues.apache.org/jira/browse/IGNITE-12281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-12281. - Resolution: Not A Problem > Data search from Ignite Cache value object > -- > > Key: IGNITE-12281 > URL: https://issues.apache.org/jira/browse/IGNITE-12281 > Project: Ignite > Issue Type: Wish >Reporter: ROHIT SANGWAN >Priority: Major > > Hi Team, > > I am solution for data look up from Ignite cache value. I found multiple > operation where I can use key to get the value. But I have a use case where I > want to apply search on few attributes of value on a certain cache. I tried > scan query but its very costly operation. Please help me to find a effective > solution. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10771) Print troubleshooting hint when exchange latch got stucked
[
https://issues.apache.org/jira/browse/IGNITE-10771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko updated IGNITE-10771:
-
Fix Version/s: 2.8
> Print troubleshooting hint when exchange latch got stucked
> --
>
> Key: IGNITE-10771
> URL: https://issues.apache.org/jira/browse/IGNITE-10771
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Minor
> Labels: usability
> Fix For: 2.8
>
>
> Sometimes users face with a problem when exchange latch can't be completed:
> {noformat}
> 2018-12-12 07:07:57:563 [exchange-worker-#42] WARN
> o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture:488 - Unable to await
> partitions release latch within timeout: ClientLatch
> [coordinator=ZookeeperClusterNode [id=6b9fc6e4-5b6a-4a98-be4d-6bc1aa5c014c,
> addrs=[172.17.0.1, 10.0.230.117, 0:0:0:0:0:0:0:1%lo, 127.0.0.1], order=3,
> loc=false, client=false], ackSent=true, super=CompletableLatch [id=exchange,
> topVer=AffinityTopologyVersion [topVer=45, minorTopVer=1]]]
> {noformat}
> It may indicate that some node in a cluster can' t finish partitions release
> (finish all ongoing operations at the previous topology version) or it can be
> silent network problem.
> We should print to log a hint how to troubleshoot it to reduce the number of
> questions about such problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-10771) Print troubleshooting hint when exchange latch got stucked
[
https://issues.apache.org/jira/browse/IGNITE-10771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko reassigned IGNITE-10771:
Assignee: Pavel Kovalenko
> Print troubleshooting hint when exchange latch got stucked
> --
>
> Key: IGNITE-10771
> URL: https://issues.apache.org/jira/browse/IGNITE-10771
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Minor
> Labels: usability
>
> Sometimes users face with a problem when exchange latch can't be completed:
> {noformat}
> 2018-12-12 07:07:57:563 [exchange-worker-#42] WARN
> o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture:488 - Unable to await
> partitions release latch within timeout: ClientLatch
> [coordinator=ZookeeperClusterNode [id=6b9fc6e4-5b6a-4a98-be4d-6bc1aa5c014c,
> addrs=[172.17.0.1, 10.0.230.117, 0:0:0:0:0:0:0:1%lo, 127.0.0.1], order=3,
> loc=false, client=false], ackSent=true, super=CompletableLatch [id=exchange,
> topVer=AffinityTopologyVersion [topVer=45, minorTopVer=1]]]
> {noformat}
> It may indicate that some node in a cluster can' t finish partitions release
> (finish all ongoing operations at the previous topology version) or it can be
> silent network problem.
> We should print to log a hint how to troubleshoot it to reduce the number of
> questions about such problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949530#comment-16949530
]
Nikolai Kulagin edited comment on IGNITE-9160 at 10/11/19 3:07 PM:
---
[~mmuzaf], I created new pull request
[#6967|https://github.com/apache/ignite/pull/6967], added [^reproduce.txt] with
a test method for reproducing bugs in equals methods, and added [^check.txt]
with a test method for checking fixes.
was (Author: zzzadruga):
[~mmuzaf], I created new pull request
[#6967|[https://github.com/apache/ignite/pull/6967]], added [^reproduce.txt]
with a test method for reproducing bugs in equals methods, and added
[^check.txt] with a test method for checking fixes.
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.9
>
> Attachments: check.txt, reproduce.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949530#comment-16949530
]
Nikolai Kulagin commented on IGNITE-9160:
-
[~mmuzaf], I created new pull request #6967, added [^reproduce.txt] with a test
method for reproducing bugs in equals methods, and added [^check.txt] with a
test method for checking fixes.
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.9
>
> Attachments: check.txt, reproduce.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949530#comment-16949530
]
Nikolai Kulagin edited comment on IGNITE-9160 at 10/11/19 3:06 PM:
---
[~mmuzaf], I created new pull request
[#6967|[https://github.com/apache/ignite/pull/6967]], added [^reproduce.txt]
with a test method for reproducing bugs in equals methods, and added
[^check.txt] with a test method for checking fixes.
was (Author: zzzadruga):
[~mmuzaf], I created new pull request #6967, added [^reproduce.txt] with a test
method for reproducing bugs in equals methods, and added [^check.txt] with a
test method for checking fixes.
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.9
>
> Attachments: check.txt, reproduce.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12284) When service class not found on any server nodes, service not deployed without any error
Ilya Kasnacheev created IGNITE-12284:
Summary: When service class not found on any server nodes, service
not deployed without any error
Key: IGNITE-12284
URL: https://issues.apache.org/jira/browse/IGNITE-12284
Project: Ignite
Issue Type: Bug
Components: managed services
Reporter: Ilya Kasnacheev
When service class presents on client node but not on server node, the
following is printed on server:
{code}
[17:57:43,398][SEVERE][srvc-deploy-#44][GridServiceProcessor] Failed to
initialize service (service will not be deployed): FService
class org.apache.ignite.IgniteCheckedException: com.gridgain.datetest.MyService
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10174)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.copyAndInject(GridServiceProcessor.java:1440)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.redeploy(GridServiceProcessor.java:1361)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.processAssignment(GridServiceProcessor.java:1988)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.onSystemCacheUpdated(GridServiceProcessor.java:1615)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.access$300(GridServiceProcessor.java:126)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor$ServiceEntriesListener$1.run0(GridServiceProcessor.java:1597)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor$DepRunnable.run(GridServiceProcessor.java:2064)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.binary.BinaryInvalidTypeException:
com.gridgain.datetest.MyService
at
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:707)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1758)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1717)
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:313)
at
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:102)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10168)
... 10 more
Caused by: java.lang.ClassNotFoundException: com.gridgain.datetest.MyService
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8775)
at
org.apache.ignite.internal.MarshallerContextImpl.getClass(MarshallerContextImpl.java:349)
at
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:698)
... 16 more
{code}
but on client, ServiceDeploymentException is not thrown. Instead, deploy
returns normally.
Code to reproduce:
{code}
public class ServiceStarterMain {
public static void main(String[] args) {
Ignition.setClientMode(true);
Ignite ignite = Ignition.start();
ServiceConfiguration serviceConfiguration = new ServiceConfiguration();
serviceConfiguration.setName("FService");
serviceConfiguration.setMaxPerNodeCount(4);
serviceConfiguration.setTotalCount(10);
serviceConfiguration.setService(new MyService());
ignite.services().deploy(serviceConfiguration); // Exception expected,
but does not happen
}
}
{code}
against a blank Ignite node started from bin distro.
This affects Java and .Net.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Kulagin updated IGNITE-9160:
Attachment: reproduce.txt
check.txt
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.9
>
> Attachments: check.txt, reproduce.txt
>
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12268) Adds possibility to set up custom REST processor.
[ https://issues.apache.org/jira/browse/IGNITE-12268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949377#comment-16949377 ] Nikolay Izhikov commented on IGNITE-12268: -- LGTM > Adds possibility to set up custom REST processor. > - > > Key: IGNITE-12268 > URL: https://issues.apache.org/jira/browse/IGNITE-12268 > Project: Ignite > Issue Type: Improvement >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > It's needed to add ability to configure your own REST processor via > functionality of Ignite plugins. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12279) [ML] Add support for using H2O MOJO models for inference
[ https://issues.apache.org/jira/browse/IGNITE-12279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-12279: - Fix Version/s: 2.9 > [ML] Add support for using H2O MOJO models for inference > > > Key: IGNITE-12279 > URL: https://issues.apache.org/jira/browse/IGNITE-12279 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 2.9 >Reporter: Michal >Assignee: Alexey Zinoviev >Priority: Major > Fix For: 2.9 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We would like to see support for using H2O MOJO models for inference (similar > to xgboost/mleap) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12279) [ML] Add support for using H2O MOJO models for inference
[ https://issues.apache.org/jira/browse/IGNITE-12279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-12279: - Affects Version/s: 2.9 > [ML] Add support for using H2O MOJO models for inference > > > Key: IGNITE-12279 > URL: https://issues.apache.org/jira/browse/IGNITE-12279 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 2.9 >Reporter: Michal >Assignee: Alexey Zinoviev >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > We would like to see support for using H2O MOJO models for inference (similar > to xgboost/mleap) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12279) [ML] Add support for using H2O MOJO models for inference
[ https://issues.apache.org/jira/browse/IGNITE-12279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-12279: - Summary: [ML] Add support for using H2O MOJO models for inference (was: Add support for using H2O MOJO models for inference) > [ML] Add support for using H2O MOJO models for inference > > > Key: IGNITE-12279 > URL: https://issues.apache.org/jira/browse/IGNITE-12279 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Michal >Assignee: Alexey Zinoviev >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > We would like to see support for using H2O MOJO models for inference (similar > to xgboost/mleap) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12279) Add support for using H2O MOJO models for inference
[ https://issues.apache.org/jira/browse/IGNITE-12279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev reassigned IGNITE-12279: Assignee: Alexey Zinoviev > Add support for using H2O MOJO models for inference > --- > > Key: IGNITE-12279 > URL: https://issues.apache.org/jira/browse/IGNITE-12279 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Michal >Assignee: Alexey Zinoviev >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > We would like to see support for using H2O MOJO models for inference (similar > to xgboost/mleap) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12271) Persistence can't read pages from disk on Big Endian architectures
[
https://issues.apache.org/jira/browse/IGNITE-12271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949335#comment-16949335
]
Alexey Goncharuk commented on IGNITE-12271:
---
Good, agree with a 2-phase change. LGTM.
> Persistence can't read pages from disk on Big Endian architectures
> --
>
> Key: IGNITE-12271
> URL: https://issues.apache.org/jira/browse/IGNITE-12271
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> So we are trying to start master on Big Endian, and we get the following
> exceptions:
> {code}
> Runtime failure on row: Row@5bf1ee15[ snip, ver: GridCacheVersion
> [topVer=180723326, order=1569259166164, nodeOrder=1] ][ 1307496, 32211, 3, 0
> ]" [5-197]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
> ... 41 more
> Caused by: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@5bf1ee15[ snip], ver: GridCacheVersion
> [topVer=180723326, order=1569259166164, nodeOrder=1] ][ 1307496, 32211, 3, 0 ]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2320)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2267)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:323)
> ... 38 more
> Caused by: java.lang.IllegalStateException: Failed to get page IO instance
> (page content is corrupted)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:84)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:96)
> at
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:153)
> at
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:107)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2RowFactory.getRow(H2RowFactory.java:61)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.createRowFromLink(H2Tree.java:221)
> at
> org.apache.ignite.internal.processors.query.h2.database.io.AbstractH2ExtrasLeafIO.getLookupRow(AbstractH2ExtrasLeafIO.java:153)
> at
> org.apache.ignite.internal.processors.query.h2.database.io.AbstractH2ExtrasLeafIO.getLookupRow(AbstractH2ExtrasLeafIO.java:35)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12283) Access restriction to IgniteKernal
Denis Garus created IGNITE-12283: Summary: Access restriction to IgniteKernal Key: IGNITE-12283 URL: https://issues.apache.org/jira/browse/IGNITE-12283 Project: Ignite Issue Type: Task Reporter: Denis Garus IgniteKernal allows a user-defined code to get access to the internal features of Ignite. That behavior leads to security lack. We must encapsulate _IgniteKernal_ to restrict access to it from user-defined code. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12271) Persistence can't read pages from disk on Big Endian architectures
[
https://issues.apache.org/jira/browse/IGNITE-12271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949291#comment-16949291
]
Ignite TC Bot commented on IGNITE-12271:
{panel:title=Branch: [pull/6953/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4673521&buildTypeId=IgniteTests24Java8_RunAll]
> Persistence can't read pages from disk on Big Endian architectures
> --
>
> Key: IGNITE-12271
> URL: https://issues.apache.org/jira/browse/IGNITE-12271
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> So we are trying to start master on Big Endian, and we get the following
> exceptions:
> {code}
> Runtime failure on row: Row@5bf1ee15[ snip, ver: GridCacheVersion
> [topVer=180723326, order=1569259166164, nodeOrder=1] ][ 1307496, 32211, 3, 0
> ]" [5-197]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
> ... 41 more
> Caused by: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@5bf1ee15[ snip], ver: GridCacheVersion
> [topVer=180723326, order=1569259166164, nodeOrder=1] ][ 1307496, 32211, 3, 0 ]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2320)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2267)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:323)
> ... 38 more
> Caused by: java.lang.IllegalStateException: Failed to get page IO instance
> (page content is corrupted)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:84)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:96)
> at
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:153)
> at
> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:107)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2RowFactory.getRow(H2RowFactory.java:61)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.createRowFromLink(H2Tree.java:221)
> at
> org.apache.ignite.internal.processors.query.h2.database.io.AbstractH2ExtrasLeafIO.getLookupRow(AbstractH2ExtrasLeafIO.java:153)
> at
> org.apache.ignite.internal.processors.query.h2.database.io.AbstractH2ExtrasLeafIO.getLookupRow(AbstractH2ExtrasLeafIO.java:35)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12117) Historical rebalance should NOT be processed in striped way
[
https://issues.apache.org/jira/browse/IGNITE-12117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov reassigned IGNITE-12117:
--
Assignee: Alexei Scherbakov
> Historical rebalance should NOT be processed in striped way
> ---
>
> Key: IGNITE-12117
> URL: https://issues.apache.org/jira/browse/IGNITE-12117
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Alexei Scherbakov
>Priority: Major
> Labels: iep-16
> Fix For: 2.9
>
>
> Test
> {{org.apache.ignite.internal.processors.cache.transactions.TxPartitionCounterStateConsistencyTest#testPartitionConsistencyWithBackupsRestart}}
> have failure on attempt to handle historical rebalance using un-striped pool.
> You can reproduce it by replacing
> {noformat}
> if (historical) // Can not be reordered.
>
> ctx.kernalContext().getStripedRebalanceExecutorService().execute(r,
> Math.abs(nodeId.hashCode()));
> {noformat}
> with
> {noformat}
> if (historical) // Can be reordered?
> ctx.kernalContext().getRebalanceExecutorService().execute(r);
> {noformat}
> and you will gain the following
> {noformat}
> ava.lang.AssertionError: idle_verify failed on 1 node.
> idle_verify check has finished, found 7 conflict partitions:
> [counterConflicts=0, hashConflicts=7]
> Hash conflicts:
> Conflict partition: PartitionKeyV2 [grpId=1544803905, grpName=default,
> partId=23]
> Partition instances: [PartitionHashRecordV2 [isPrimary=false,
> consistentId=nodetransactions.TxPartitionCounterStateConsistencyHistoryRebalanceTest1,
> updateCntr=707143, partitionState=OWNING, size=495, partHash=-1503789370],
> PartitionHashRecordV2 [isPrimary=false,
> consistentId=nodetransactions.TxPartitionCounterStateConsistencyHistoryRebalanceTest2,
> updateCntr=707143, partitionState=OWNING, size=494, partHash=-1538739200]]
> Conflict partition: PartitionKeyV2 [grpId=1544803905, grpName=default,
> partId=8]
>
> {noformat}
> So, we need to investigate reasons and provide proper historical rebalance
> refactoring to use the unstriped pool, if possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12282) Access restriction to the internal package of Ignite
[
https://issues.apache.org/jira/browse/IGNITE-12282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Garus updated IGNITE-12282:
-
Ignite Flags: Docs Required (was: Docs Required,Release Notes Required)
> Access restriction to the internal package of Ignite
>
>
> Key: IGNITE-12282
> URL: https://issues.apache.org/jira/browse/IGNITE-12282
> Project: Ignite
> Issue Type: Task
>Reporter: Denis Garus
>Priority: Major
>
> A user-defined code shouldn't have access to _org.apache.ignite.internal_.*
> that is the internal package of Ignite.
> To restrict a user-defined code, we need to set the package name to the
> _package.access_ security property.
> To grand access to a package, we have to use _accessClassInPackage.\{package
> name}_ runtime permission.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12282) Access restriction to the internal package of Ignite
Denis Garus created IGNITE-12282:
Summary: Access restriction to the internal package of Ignite
Key: IGNITE-12282
URL: https://issues.apache.org/jira/browse/IGNITE-12282
Project: Ignite
Issue Type: Task
Reporter: Denis Garus
A user-defined code shouldn't have access to _org.apache.ignite.internal_.*
that is the internal package of Ignite.
To restrict a user-defined code, we need to set the package name to the
_package.access_ security property.
To grand access to a package, we have to use _accessClassInPackage.\{package
name}_ runtime permission.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-10683) Prepare process of packaging and delivering thin clients
[
https://issues.apache.org/jira/browse/IGNITE-10683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949217#comment-16949217
]
Peter Ivanov commented on IGNITE-10683:
---
Is there a process of thin clients release currently?
> Prepare process of packaging and delivering thin clients
>
>
> Key: IGNITE-10683
> URL: https://issues.apache.org/jira/browse/IGNITE-10683
> Project: Ignite
> Issue Type: Task
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.8
>
>
> # **NodeJs client**
> #* +Instruction+:
> https://github.com/nobitlost/ignite/blob/ignite--docs/modules/platforms/nodejs/README.md#publish-ignite-nodejs-client-on-npmjscom-instruction
> #* +Uploaded+: https://www.npmjs.com/package/apache-ignite-client
> # **PHP client**
> #* +Instruction+:
> https://github.com/nobitlost/ignite/blob/ignite-7783-docs/modules/platforms/php/README.md#release-the-client-in-the-php-package-repository-instruction
> {panel}
> Cannot be uploaded on Packagist as the client should be in a dedicated
> repository for that -
> https://issues.apache.org/jira/browse/IGNITE-7783?focusedCommentId=16595476&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16595476
> Installation from the sources works.
> {panel}
> # **Python client**
> I have already registered the package `pyignite` on PyPI[1]. The person who
> is going to take the responsibility of maintaining it should create an
> account on PyPI and mail me in private, so that I can grant them the
> necessary rights. They also must install twine[3].
> The process of packaging is well described in the packaging tutorial[2]. In
> the nutshell, the maintainer must do the following:
> ## Clone/pull the sources from the git repository,
> ## Enter the directory in which the `setup.py` is resides (“the setup
> directory”), in our case it is `modules/platforms/python`.
> ## Create the packages with the command `python3 setup.py sdist bdist_wheel`.
> The packages will be created in `modules/platforms/python/dist` folder.
> ## Upload packages with twine: `twine upload dist/*`.
> It is very useful to have a dedicated Python virtual environment prepared to
> perform steps 3-4. Just do an editable install of `pyignite` into that
> environment from the setup directory: `pip3 install -e .` You can also
> install twine (`pip install twine`) in it.
> Consider also making a `.pypirc` file to save time on logging in to PyPI.
> Newest version of `twine` is said to support keyrings on Linux and Mac, but I
> have not tried this yet.
> [1] https://pypi.org/project/pyignite/
> [2] https://packaging.python.org/tutorials/packaging-projects/
> [3] https://twine.readthedocs.io/en/latest/
> Some other notes on PyPI and versioning.
> - The package version is located in the `setup.py`, it is a `version`
> argument of the `setuptools.setup()` function. Editing the `setup.py` is the
> only way to set the package version.
> - You absolutely can not replace a package in PyPI (hijacking prevention). If
> you have published the package by mistake, all you can do is delete the
> unwanted package, increment the version counter in `setup.py`, and try again.
> - If you upload the package through the web interface of PyPI (without
> twine), the package description will be garbled. Web interface does not
> support markdown.
> Anyway, I would like to join in the congratulations on successful release.
> Kudos to the team.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
