[jira] [Created] (IGNITE-8824) .NET: Invalid header on deserialization
Roman Guseinov created IGNITE-8824:
--
Summary: .NET: Invalid header on deserialization
Key: IGNITE-8824
URL: https://issues.apache.org/jira/browse/IGNITE-8824
Project: Ignite
Issue Type: Bug
Components: binary, platforms
Affects Versions: 2.5
Reporter: Roman Guseinov
Attachments: InteropreabilityTest.cs, ServerNode.java
The issue happens when we save an object with java.util.Date field in Java and
retrieves that one on .NET side (DateTime). According to the docs these types
should be compatible [1].
{code:java}
Apache.Ignite.Core.Binary.BinaryObjectException: 'Invalid header on
deserialization [pos=34, hdr=11]'
{code}
The workaround is java.sql.Timestamp instead of Date type.
Java and C# code examples to reproduce the issue are attached:
[^ServerNode.java][^InteropreabilityTest.cs]
[1]
[https://apacheignite-net.readme.io/v2.1/docs/platform-interoperability#section-type-compatibility]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #4220: IGNITE-8749: storage error handling fix.
GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/4220 IGNITE-8749: storage error handling fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/x-kreator/ignite ignite-8749-fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4220.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4220 commit cfdfd8a60c3964e298573d4baf0c2ccd223531da Author: Dmitriy Sorokin Date: 2018-06-19T00:51:09Z IGNITE-8749: storage error handling fix. ---
Re: Apache Ignite support is added to universal command-line interface for SQL databases
Denis, I think we should list this integration somewhere on the Ignite website. On top of that, the integration uses Ignite Go client, which also deserves a mention. D. On Mon, Jun 18, 2018 at 9:35 AM, Denis Magda wrote: > Kenneth, thanks for supporting Ignite at usql level! Excellent news! What's > the Ignite version used there and what's the update policy? > > Parchi, could you document Ignite usage together with usql? > > -- > Denis > > > > > > On Sun, Jun 17, 2018 at 1:40 AM Aleksandr Sokolovskii > wrote: > > > Hi Apache Ignite Community, > > > > Thanks to Kenneth Shaw for Apache Ignite support to universal > command-line > > interface for SQL databases. > > You can find details here: > > https://github.com/xo/usql > > > > Thanks, > > Aleksandr > > > > >
[GitHub] ignite pull request #4219: Ignite 1.9 master no reconnect
GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/4219 Ignite 1.9 master no reconnect You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.9-master-no-reconnect Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4219.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4219 commit c82e25d67a2f6825a27d26933199a436f6eabba2 Author: Dmitriy Govorukhin Date: 2017-04-07T11:28:22Z IGNITE-4889 - Changed Hibernate integration to use custom keys (cherry picked from commit 6b62a20) commit a352951d91edde9c0029a8bf435d61b4a7cd8c11 Author: Andrey V. Mashenkov Date: 2017-07-04T17:24:52Z IGNITE-4831: Add an option to disable MBeans. commit e4d141e97ab4ec34b5fe6a7bc599413223944438 Author: dkarachentsev Date: 2017-07-14T11:40:02Z IGNITE-5103 - Server drops client node from cluster when no heartbeat messages received in interval heartBeatsFrequency * maxMissedClientHeartBeats. commit 45573945066113fd29548699f23c2bc9f22cef36 Author: Tikhonov Nikolay Date: 2017-06-21T14:55:05Z ignite-5489 Fixed possible connection leaks when loadPreviousValue set to true commit 37535634ef3325aaf9923fd17d24038dfd5cee38 Author: agura Date: 2017-07-11T13:24:54Z ignite-5722 Cache entries stay in onheap after scan query execution for OFFHEAP_TIRED cache with expiry policy commit c3e2eebeccbdc4bb3a7a0a70d09a8a7b63399c2c Author: Evgenii Zhuravlev Date: 2017-07-18T15:50:48Z IGNITE 5776 Add option to turn on filter reachable addresses in TcpCommunicationSpi commit 97d3f42c1c95a6aafce1d0c300ccfe6708398c17 Author: shtykh_roman Date: 2016-09-07T05:35:31Z IGNITE-3809: Fix for ArrayIndexOutOfBoundsException in GridUnsafeLru. (cherry picked from commit 31b9bb8) commit c2062d52a227dda5afee560d80c3bb4dd2ce09eb Author: dkarachentsev Date: 2017-07-19T05:41:46Z Remove empty test_utils.cpp commit 45cbba4853bab1ba4ffe2ea0d3add99a9d454aab Author: dkarachentsev Date: 2017-07-19T07:44:04Z IGNITE-5768 - Retry resolving class name from marshaller cache and .classname file. commit f24969f7e908645444df622642967a5f7fd3db23 Author: Evgenii Zhuravlev Date: 2017-07-19T16:30:07Z IGNITE 5775 JobsProcessor fix bug with delay in compute commit e5aab82f5629c2705e9bc82a7676f63c7c77062a Author: dkarachentsev Date: 2017-07-20T07:37:08Z Merge branch 'ignite-1.7.13' into ignite-1.8.9 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/jdbc2/JdbcPreparedStatement.java # modules/core/src/main/java/org/apache/ignite/internal/util/IgniteUtils.java commit 1544d3b63974ef8a96694cfc0681548fb4625a59 Author: Evgenii Zhuravlev Date: 2017-07-24T07:18:59Z Merge branch 'ignite-1.7.4-p2' into ignite-1.7.14 commit 7e5b479a9c48a6e272f8883f16d0ffa454e44046 Author: Andrey V. Mashenkov Date: 2017-07-24T10:27:52Z Merge remote-tracking branch 'origin/ignite-1.7.12-p1' into ignite-1.7.14 commit cc89a6a224ade08c92f44211dc144dc806c2b400 Author: dkarachentsev Date: 2017-07-26T08:19:19Z Merge branch 'ignite-1.8.9' into ignite-1.9.5 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/MarshallerContextImpl.java # modules/core/src/test/java/org/apache/ignite/internal/processors/datastreamer/DataStreamerImplSelfTest.java # modules/indexing/src/test/java/org/apache/ignite/testsuites/IgniteCacheQuerySelfTestSuite2.java # modules/platforms/cpp/core-test/src/test_utils.cpp commit f3adb9559b42698771b0b9b5116dd535446d2bef Author: vsisko Date: 2017-07-26T08:40:19Z IGNITE-5781 Visor throws ClassCastException if cache store implementation is other than CacheJdbcPojoStore. commit a58688f6cc6c5b114dcdd1b2fde43b7e1e5e0732 Author: vsisko Date: 2017-07-26T08:40:19Z IGNITE-5781 Visor throws ClassCastException if cache store implementation is other than CacheJdbcPojoStore. (cherry picked from commit f3adb95) commit 5b8963e38254fcac3bdd255a95adf9f733ce08f2 Author: vsisko Date: 2017-07-26T08:40:19Z IGNITE-5781 Visor throws ClassCastException if cache store implementation is other than CacheJdbcPojoStore. (cherry picked from commit f3adb95) commit 6c6264e93c378ff3f083528b46e673fefc76f471 Author: vsisko Date: 2017-07-26T08:48:27Z Merge remote-tracking branch 'community/ignite-1.9.5' into ignite-1.9.5 commit b7d1fb25ceba20b82631bb2e926a0ad52bf19e9d Author: sboikov Date: 2017-07-20T14:43:17Z Do not process partition exchange messages in striped pool. (cherry picked from commit 3a33706) commit c338bb9f5ac8f34dccbac1f7058765c5ce4549a4 Author: sboikov Date: 2017-07-20T14:49:55Z Removed unnecessary discoCache.updateAlives.
Re: Separate binaries for thin clients and drivers
On Mon, Jun 18, 2018 at 9:45 AM, Denis Magda wrote: > Guys, > > Have a look at Hazelcast. They provide both approaches - installation with > a package management system + binary (or zip archives downloads): > https://hazelcast.org/clients-languages/ > > It will be great to provide Ignite community with the same usability. > Agree with Denis. For example, Maven for Java is not an installation, is a project-dependency import. We need a separate ZIP file for Java client which will include the license information, examples, documentation, and any additional dependencies if needed. I am sure the same approach will have to be put in place for many other clients.
Re: Separate binaries for thin clients and drivers
Guys, Have a look at Hazelcast. They provide both approaches - installation with a package management system + binary (or zip archives downloads): https://hazelcast.org/clients-languages/ It will be great to provide Ignite community with the same usability. -- Denis On Mon, Jun 18, 2018 at 12:20 AM Igor Sapego wrote: > So, it seems, like it only has sense for ODBC Windows binaries. > For Linux there are also packages that should also be used. > Best Regards, > Igor > > > On Mon, Jun 18, 2018 at 10:04 AM Pavel Tupitsyn > wrote: > > > Same thing with package manager for .NET (NuGet). > > And same with Java, actually (Maven). > > > > In my understanding, most people use package managers and don't download > > ZIP archives. > > Package managers are more convenient and easy to use. It is a modern way. > > > > > > On Sun, Jun 17, 2018 at 11:28 AM, Aleksandr Sokolovskii < > amso...@gmail.com > > > > > wrote: > > > > > Hi All, > > > > > > The same situation is for Go lang also. > > > There are no binaries. > > > Libraries are installed from source code repo, etc.: > > > > > > go get -u github.com/amsokol/ignite-go-client > > > > > > So the proposal is not really applicable to Go lang client. > > > > > > Thanks, > > > Aleksandr > > > > > > From: Pavel Petroshenko > > > Sent: 16 июня 2018 г. 21:10 > > > To: Denis Magda > > > Cc: dev > > > Subject: Re: Separate binaries for thin clients and drivers > > > > > > Hi Denis, > > > > > > There are no "binaries" for Node.js and Python that you can download. > > These > > > Thin Clients are distributed and installed by a package management > system > > > (npm, pip): which resolves all the dependencies and deploys necessary > > > components to the appropriate system locations. So instead of > > downloading a > > > Node or Python package binary, the package management systems should be > > > used to properly install it: > > > > > > Node.js: $ npm install <...> > > > or > > > Python: $ pip install <...> > > > > > > So the proposal is not really applicable to these clients. > > > > > > Pavel > > > > > > > > > > > > On Sat, Jun 16, 2018 at 12:45 AM, Dmitriy Setrakyan < > > dsetrak...@apache.org > > > > > > > wrote: > > > > > > > +1 > > > > > > > > On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda > > wrote: > > > > > > > > > Igniters, > > > > > > > > > > Presently, all our thin clients and SQL drivers are stored in the > > main > > > > > Ignite repository. That's totally fine, I wouldn't change anything > in > > > > here. > > > > > > > > > > But, what I would encourage us to contemplate on is how a user gets > > and > > > > > downloads those binaries. Basically, the user has to download the > > whole > > > > > Ignite distribution even if he needs just a JDBC driver or Node.JS > > thin > > > > > driver. > > > > > > > > > > The proposal is pretty simple. In addition to the main > distribution, > > > > let's > > > > > prepare separate ZIP archives with binaries for: > > > > > > > > > >- JDBC > > > > >- ODBC > > > > >- Thin clients (Java, C#, Node.JS, Python, etc.) > > > > > > > > > > The binaries would be available for downloads on the main page: > > > > > https://ignite.apache.org/download.cgi > > > > > > > > > > Thoughts? Supporters and opposers, please speak out. > > > > > > > > > > -- > > > > > Denis > > > > > > > > > > > > > > > > > >
Re: Apache Ignite support is added to universal command-line interface for SQL databases
Kenneth, thanks for supporting Ignite at usql level! Excellent news! What's the Ignite version used there and what's the update policy? Parchi, could you document Ignite usage together with usql? -- Denis On Sun, Jun 17, 2018 at 1:40 AM Aleksandr Sokolovskii wrote: > Hi Apache Ignite Community, > > Thanks to Kenneth Shaw for Apache Ignite support to universal command-line > interface for SQL databases. > You can find details here: > https://github.com/xo/usql > > Thanks, > Aleksandr > >
[GitHub] ignite pull request #4070: IGNITE-8601 Add to control.sh utility information...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4070 ---
[GitHub] ignite pull request #4194: IGNITE-8804 Windows WSL configuration has to be a...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4194 ---
[GitHub] ignite pull request #4202: IGNITE-8707 header is accounted during calculatio...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4202 ---
[GitHub] ignite pull request #4212: IGNITE-8815 Ease enabling wal mangement in contro...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4212 ---
[jira] [Created] (IGNITE-8823) Incorrect transaction state in tx manager
Andrey Gura created IGNITE-8823:
---
Summary: Incorrect transaction state in tx manager
Key: IGNITE-8823
URL: https://issues.apache.org/jira/browse/IGNITE-8823
Project: Ignite
Issue Type: Bug
Reporter: Andrey Gura
Reproducable by test
{{org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest#testCreateConsistencyMultithreaded}}:
{noformat}
18:34:40,701][SEVERE][sys-stripe-0-#44%ignite%][GridCacheIoManager] Failed
processing message [senderId=e273c3f8-02ed-4201-9ac8-09f9ab6a1d31,
msg=GridNearTxPrepareResponse [pending=[],
futId=b4df8831461-9735f9d5-79a0-47a3-a951-e62a03af71ef, miniId=1,
dhtVer=GridCacheVersion [topVer=140816081, order=1529336085358, nodeOrder=3],
writeVer=GridCacheVersion [topVer=140816081, order=1529336085360, nodeOrder=3],
ownedVals=null, retVal=GridCacheReturn [v=null, cacheObj=null, success=true,
invokeRes=true, loc=true, cacheId=0], clientRemapVer=null,
super=GridDistributedTxPrepareResponse [txState=IgniteTxImplicitSingleStateImpl
[init=true, recovery=false], part=-1, err=null,
super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=140816081,
order=1529336085224, nodeOrder=1], committedVers=null, rolledbackVers=null,
cnt=0, super=GridCacheIdMessage [cacheId=0]
java.lang.AssertionError: true instead of GridCacheReturnCompletableWrapper
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.removeTxReturn(IgniteTxManager.java:1098)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.ackBackup(GridNearTxFinishFuture.java:533)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.doFinish(GridNearTxFinishFuture.java:500)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.finish(GridNearTxFinishFuture.java:417)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$19.apply(GridNearTxLocal.java:3341)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$19.apply(GridNearTxLocal.java:3335)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
at
org.apache.ignite.internal.processors.cache.GridCacheCompoundFuture.onDone(GridCacheCompoundFuture.java:56)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.onComplete(GridNearOptimisticTxPrepareFuture.java:310)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.onDone(GridNearOptimisticTxPrepareFuture.java:288)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.onDone(GridNearOptimisticTxPrepareFuture.java:78)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
at
org.apache.ignite.internal.util.future.GridCompoundFuture.checkComplete(GridCompoundFuture.java:285)
at
org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:144)
at
org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:45)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture$MiniFuture.onResult(GridNearOptimisticTxPrepareFuture.java:1017)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.onResult(GridNearOptimisticTxPrepareFuture.java:198)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareResponse(IgniteTxHandler.java:654)
at
[GitHub] ignite pull request #3652: IGNITE-7770 A bunch of changes to fix tx timeout ...
Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3652 ---
[GitHub] ignite pull request #3843: Ignite 7770 2
Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3843 ---
[GitHub] ignite pull request #3861: IGNITE-8303: Avoided failure handler invocation w...
Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3861 ---
[GitHub] ignite pull request #3870: IGNITE-8312: Simplified the choice of exception t...
Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3870 ---
[GitHub] ignite pull request #4121: IGNITE-8562: Squashed partial commits.
Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/4121 ---
[GitHub] ignite pull request #4173: IGNITE-8562: As single large commit.
Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/4173 ---
[jira] [Created] (IGNITE-8822) SQL: Failed to run map query remotely.
Pavel Kuznetsov created IGNITE-8822: --- Summary: SQL: Failed to run map query remotely. Key: IGNITE-8822 URL: https://issues.apache.org/jira/browse/IGNITE-8822 Project: Ignite Issue Type: Bug Components: sql Environment: reproduce on ignite cluster with 1 node. Default data region should be increased to 4 GiB. Reporter: Pavel Kuznetsov Given tables and indexes created (see attached create_tables.sql and create_indexes.sql) If we run 11.sql we'll get an error: "Error: class org.apache.ignite.IgniteException: Failed to generate REDUCE query. Data table found: PUBLIC.PARTSUPP" see full output in attached 11-out.txt and 11-server-err.txt (server errors) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4218: IGNITE-8821: Huge logs on BPlusTreeSelfTest put/r...
GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/4218 IGNITE-8821: Huge logs on BPlusTreeSelfTest put/remove family tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/x-kreator/ignite ignite-8821 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4218.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4218 commit 1d6014873c11e9285dcda13f45363ce129796c55 Author: Dmitriy Sorokin Date: 2018-06-18T13:57:35Z IGNITE-8821: Huge logs on BPlusTreeSelfTest put/remove family tests. ---
[jira] [Created] (IGNITE-8821) Huge logs on BPlusTreeSelfTest put/remove family tests
Dmitriy Sorokin created IGNITE-8821: --- Summary: Huge logs on BPlusTreeSelfTest put/remove family tests Key: IGNITE-8821 URL: https://issues.apache.org/jira/browse/IGNITE-8821 Project: Ignite Issue Type: Test Components: general Reporter: Dmitriy Sorokin Assignee: Dmitriy Sorokin Fix For: 2.6 A printLocks method generates huge count of ## XX log lines without any more info assigned to. Avoiding the output of unnecessary non-informative lines is suggested. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4217: IGNITE-8820: Add ability to read new value of txT...
GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/4217 IGNITE-8820: Add ability to read new value of txTimeoutOnPartitionMap⦠â¦Exchange while exchange future runs. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ivandasch/ignite ignite-8820 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4217.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4217 commit 44dc068d5d9ffb4bbce8986a4195299ceb5b697c Author: Ivan Daschinskiy Date: 2018-06-18T10:48:45Z IGNITE-8820: Add ability to read new value of txTimeoutOnPartitionMapExchange while exchange future runs. ---
[jira] [Created] (IGNITE-8820) Add ability to accept changing txTimeoutOnPartitionMapExchange while waiting for pending transactions.
Ivan Daschinskiy created IGNITE-8820: Summary: Add ability to accept changing txTimeoutOnPartitionMapExchange while waiting for pending transactions. Key: IGNITE-8820 URL: https://issues.apache.org/jira/browse/IGNITE-8820 Project: Ignite Issue Type: Improvement Affects Versions: 2.5 Reporter: Ivan Daschinskiy Assignee: Ivan Daschinskiy Fix For: 2.6 Currently, if ExchangeFuture waits whith old value of txTimeoutOnPartitionMapExchange, new value is not accepted until next exchange starts. Sometimes it's very usefull (while timeout is too long and must be shorter applied immediatelly) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Best Effort Affinity for thin clients
I've created an IEP: [1] [1] - https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients Best Regards, Igor On Thu, Jun 14, 2018 at 4:17 PM Pavel Tupitsyn wrote: > Ok, I see, this is what I was trying to understand, and this is an > important note I think: > > * We should request AffinityFunction for each particular cache and only > enable this functionality for known functions > * Make sure that known server-side functions never change their behavior > > Thanks > > On Thu, Jun 14, 2018 at 3:39 PM, Igor Sapego wrote: > > > Vladimir is right, > > > > As far as I know, most users use affinity functions provided by Ignite. > > So we could optimize for the default case and, in future, optionally, > > let user implement their own AffinityFunction for thin clients. > > > > Best Regards, > > Igor > > > > > > On Thu, Jun 14, 2018 at 3:06 PM Vladimir Ozerov > > wrote: > > > > > Pavel, > > > > > > The idea here is that optimization will be applicable only for > well-known > > > affinity functions. E.g., we know that for rendezvous affinity, > partition > > > is "hash(key) % partitions". This is all we need to make default > affinity > > > work. > > > > > > On Thu, Jun 14, 2018 at 11:41 AM, Pavel Tupitsyn > > > > wrote: > > > > > > > AffinityFunction interface has the following method: > > > > int partition(Object key) > > > > > > > > User calls cache.put(x,y) from the client. > > > > > > > > In order to calculate the target node we have to call that partition > > > > method, > > > > and then use partition map to get the node by partition. > > > > > > > > But client does not have AffinityFunction. > > > > Where am I wrong here? > > > > > > > > On Thu, Jun 14, 2018 at 10:26 AM, Igor Sapego > > > > wrote: > > > > > > > > > Denis, that's right. > > > > > > > > > > Best Regards, > > > > > Igor > > > > > > > > > > > > > > > On Wed, Jun 13, 2018 at 10:58 PM Denis Magda > > > wrote: > > > > > > > > > > > Pavel, > > > > > > > > > > > > Most likely the client will be pulling the partitioning map > > > > periodically. > > > > > > If the local map is outdated, it won't be a big deal because a > > server > > > > > node > > > > > > that receives a request: > > > > > > > > > > > >- can redirect it to a map that owns a partition > > > > > >- will add an updated partition map to the client's response > or > > > will > > > > > >turn a special flag in the response suggesting the client do > > that > > > > > > manually. > > > > > > > > > > > > Igor, is this what you're suggesting? > > > > > > > > > > > > -- > > > > > > Denis > > > > > > > > > > > > On Wed, Jun 13, 2018 at 11:31 AM Pavel Tupitsyn < > > > ptupit...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > Hi Igor, > > > > > > > > > > > > > > How can we invoke the affinity function on the client, if we > > don't > > > > have > > > > > > the > > > > > > > implementation at hand? > > > > > > > Am I missing something? > > > > > > > > > > > > > > Thanks, > > > > > > > Pavel > > > > > > > > > > > > > > > > > > > > > On Wed, Jun 13, 2018 at 5:34 PM, Igor Sapego < > isap...@apache.org > > > > > > > > wrote: > > > > > > > > > > > > > > > Hi, Igniters, > > > > > > > > > > > > > > > > Currently, I'm working on the thin C++ client implementation. > > > > > > > > As you may already know, there is an issue with latency in > our > > > > > > > > thin clients, which also can result in performance issues > (you > > > > > > > > can see the "About Ignite Thin client performance" thread on > > > > > > > > user list). > > > > > > > > > > > > > > > > So, how about we implement some kind of "Best Effort > Affinity" > > > > > > > > for our thin clients? In my opinion, this could be possible > and > > > > > > > > may improve mean latency when using thin clients > dramatically. > > > > > > > > > > > > > > > > The scenario is following: > > > > > > > > 1. Thin client connects to one of the node from the provided > > > > > > > > address list, just as now. > > > > > > > > 2. When user create instance of CacheClient, thin client > > > > > > > > requests partition mapping for the cache. > > > > > > > > 3. Client establishes connections to nodes, which are both in > > the > > > > > > > > list, provided by user and in a server node response. > > > > > > > > 4. When user makes put/get/some other cache operation, > > > > > > > > thin client makes the best effort to send the request to the > > > node, > > > > > > > > which stores the data. > > > > > > > > 5. To update partition mapping, thin client can provide > public > > > API, > > > > > > > > or do it with some timeout. Also, we can add "miss" flag to > > cache > > > > > > > > operation response, which whill indicate, that operation was > > not > > > > > > > > local for the server node and which thin client can use to > > > > > > > > understand, that partition mapping has changed to request > > server > > > > > > > > node for an update. > > > > > > > > > > > > > > > > What do you think? > > >
[jira] [Created] (IGNITE-8819) Web Console: Edit everywhere the export buttons (2 types of design)
Vica Abramova created IGNITE-8819: - Summary: Web Console: Edit everywhere the export buttons (2 types of design) Key: IGNITE-8819 URL: https://issues.apache.org/jira/browse/IGNITE-8819 Project: Ignite Issue Type: Improvement Components: UI, wizards Reporter: Vica Abramova Assignee: Alexey Kuznetsov Attachments: New Export.png See attached -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8818) Web Console: Reduce the height of head of all tables and change the location of the content
Vica Abramova created IGNITE-8818: - Summary: Web Console: Reduce the height of head of all tables and change the location of the content Key: IGNITE-8818 URL: https://issues.apache.org/jira/browse/IGNITE-8818 Project: Ignite Issue Type: Improvement Components: UI, wizards Reporter: Vica Abramova Assignee: Alexey Kuznetsov Attachments: Table-header.png New height: 64px !Table-header.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4179: IGNITE-8184 ZookeeperDiscoverySpiTest#testTopolog...
Github user dgarus closed the pull request at: https://github.com/apache/ignite/pull/4179 ---
Re: Ignite 2.6 emergency release suggestion
Hi Petr, Who will be able to make the review for the suggested patch? I would like to freeze the branch and start preparing the release. пт, 15 июн. 2018 г. в 11:45, Petr Ivanov : > Igniters, > > > I’d like to stage for 2.6 release also this issue [1]. Corresponding PR > [2] is ready for review and merge. > This is not related to code additional configuration file for enabling > support of Windows 10 WSL Environment. > > > [1] https://issues.apache.org/jira/browse/IGNITE-8804 > [2] https://github.com/apache/ignite/pull/4194 > > > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov > wrote: > > > > Hi, > > > > Fix for IGNITE-8722 (https://issues.apache.org/jira/browse/IGNITE-8722) > is > > ready. > > > > Diff > > > > > https://git1-us-west.apache.org/repos/asf?p=ignite.git=search=refs%2Fheads%2Fignite-8722=commit=IGNITE-8722 > > > > TC looks good for me. > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1385195=buildResultsDiv=IgniteTests24Java8_JavaClient > > > > I'm ready to merge to master and 2.6 branches. > > Please approve. > > > > -- > > Alexey Kuznetsov > >
[GitHub] ignite pull request #4147: IGNITE-8565 Client marshalling improvements
Github user agura closed the pull request at: https://github.com/apache/ignite/pull/4147 ---
Re: IGNITE-640: multimap initial implementation
Amir, Everything is fine, I'll check changes this week. вс, 17 июн. 2018 г. в 6:09, Amir Akhmedov : > Anton, > I created a news PR [1]. Since it includes the same changes I did not run > TC tests on it. Please let me know if you think otherwise. > > [1] https://github.com/apache/ignite/pull/4207 > > Thanks, > Amir > > > On Wed, Jun 13, 2018 at 8:38 AM Anton Vinogradov wrote: > > > Amir, > > > > Thanks for attempt. > > As far as I can see you have all changes at this commit: > > > > > https://github.com/apache/ignite/pull/3926/commits/cd0e50e05d3860788378ebf1a29dc0525460872a > > > > You can simply apply it to local branch based on master by patch > > > > > https://github.com/apache/ignite/commit/cd0e50e05d3860788378ebf1a29dc0525460872a.patch > > > > In case you use IDEA, just apply patch from clipboard, and that's will be > > you PR. > > > > BTW, next time you can use easiest way to squash your changes - just to > > pull all changes from existing PR with squash > > > git pull https://github.com/apache/ignite.git pull/XXX/head --squash > > > > > > > > вт, 5 июн. 2018 г. в 19:34, Amir Akhmedov : > > > > > Dmitry P., Anton V., > > > I made some changes and updated the ticket. Also as was asked I tried > to > > > squash the commits into one but looks like I screwed up everything and > > the > > > PR now looks completely terrible. Since I'm not an advanced git user, > > could > > > you please check the PR and let me know if anything could be done > there? > > If > > > not I will try to create a new PR. > > > > > > Thanks, > > > Amir > > > > > > On Tue, May 29, 2018 at 10:37 AM, Dmitry Pavlov > > > > wrote: > > > > > > > Hi Amir, > > > > > > > > As far as I know, several Igniters provided some feedback in ticket. > > Are > > > > you agree? > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > чт, 10 мая 2018 г. в 20:01, Dmitry Pavlov : > > > > > > > > > Hi Amir, > > > > > > > > > > This is a very necessary contribution, the patch defenetely will > not > > be > > > > > ignored. > > > > > > > > > > Igniters, > > > > > > > > > > Who can make a review from the committers? > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > вт, 8 мая 2018 г. в 5:52, Amir Akhmedov : > > > > > > > > > >> Hi Igniters, > > > > >> > > > > >> Can someone take a look at this PR please? > > > > >> > > > > >> Thanks, > > > > >> Amir > > > > >> > > > > >> On Mon, Apr 30, 2018 at 5:28 AM, Pavel Tupitsyn < > > ptupit...@apache.org > > > > > > > > >> wrote: > > > > >> > > > > >> > Hi Amir, > > > > >> > > > > > >> > I have filed [1] for multimap in .NET, it will be done later. > > > > >> > In order to fix IgniteParityTest failures, please add the > > following > > > to > > > > >> > MissingMembers array there: > > > > >> > > > > > >> > "multimap" // IGNITE-8425 > > > > >> > > > > > >> > Thanks, > > > > >> > Pavel > > > > >> > > > > > >> > > > > > >> > [1] https://issues.apache.org/jira/browse/IGNITE-8425 > > > > >> > > > > > >> > On Sun, Apr 29, 2018 at 11:32 PM, Amir Akhmedov < > > > > >> amir.akhme...@gmail.com> > > > > >> > wrote: > > > > >> > > > > > >> > > Hi Igniters, > > > > >> > > > > > > >> > > I raised a pull request [1] for Ignite multimap [2]. TC run > [3] > > > > seems > > > > >> ok > > > > >> > to > > > > >> > > me, some tests are failed though. Can someone review it please > > and > > > > >> let me > > > > >> > > know? > > > > >> > > > > > > >> > > Thanks, > > > > >> > > Amir > > > > >> > > > > > > >> > > [1] https://github.com/apache/ignite/pull/3926 > > > > >> > > [2] https://issues.apache.org/jira/browse/IGNITE-640 > > > > >> > > [3] > > > > >> > > https://ci.ignite.apache.org/viewLog.html?buildId=1255210 > > > > >> > > b=buildResultsDiv=IgniteTests24Java8_RunAll > > > > >> > > > > > > >> > > > > > >> > > > > > > > > > > > > > > >
[GitHub] ignite pull request #4214: IGNITE-8795 Add ability to start and maintain Ten...
GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/4214 IGNITE-8795 Add ability to start and maintain TensorFlow cluster on top of Apache Ignite You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8795 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4214.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4214 commit 9a8d733f19a06aea210f8da233d28fb859570819 Author: dmitrievanthony Date: 2018-06-16T18:00:39Z IGNITE-8795 First prototype of TensorFlow Cluster manager. commit 3becae8217a8556f8f985562fb732cd081c71673 Author: Anton Dmitriev Date: 2018-06-18T11:47:43Z IGNITE-8795 Add tests to TensorFlow module and refactoring. commit 5f6ee37ebdc1f9cd852d70890ea45b63c15096c1 Author: Anton Dmitriev Date: 2018-06-18T11:50:01Z IGNITE-8795 Remove commented code. ---
[GitHub] ignite pull request #4213: IGNITE-8813 - Add ComputeJobResultPolicy to JobEv...
GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/4213 IGNITE-8813 - Add ComputeJobResultPolicy to JobEvent You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8813 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4213.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4213 commit c02a0699bc35ffb5e00827b7f07eaddce22d088b Author: dkarachentsev Date: 2018-06-18T11:23:53Z IGNITE-8813 - Add ComputeJobResultPolicy to JobEvent ---
[GitHub] ignite pull request #4212: IGNITE-8815 Ease enabling wal mangement in contro...
GitHub user macrergate opened a pull request: https://github.com/apache/ignite/pull/4212 IGNITE-8815 Ease enabling wal mangement in control.sh You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8815 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4212.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4212 commit c64f8669eab0c8964585c833441aea66132bf5d6 Author: Sergey Kosarev Date: 2018-06-18T09:32:51Z IGNITE-8815 Ease enabling wal mangement in control.sh ---
[GitHub] ignite pull request #4211: IGNITE-8203 Interrupting task can cause node fail...
GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/4211 IGNITE-8203 Interrupting task can cause node fail with PersistenceStorageIOException. You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite ignite-8203 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4211.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4211 commit c9ce18c697fe689a8ef5bd70d90d1be71367e59d Author: Aleksey Plekhanov Date: 2018-06-14T15:57:53Z IGNITE-8203 Interrupting task can cause node fail with PersistenceStorageIOException. ---
[jira] [Created] (IGNITE-8815) Ease enabling wal mangement in control.sh
Sergey Kosarev created IGNITE-8815:
--
Summary: Ease enabling wal mangement in control.sh
Key: IGNITE-8815
URL: https://issues.apache.org/jira/browse/IGNITE-8815
Project: Ignite
Issue Type: Improvement
Affects Versions: 2.6
Reporter: Sergey Kosarev
Assignee: Sergey Kosarev
Fix For: 2.6
--wal command was introduce in IGNITE-7912 under option
-DIGNITE_ENABLE_EXPERIMENTAL_COMMAND=true only.
It'd better add this option into control.sh script as a comment:
# Uncomment to enable --wal command
# JVM_OPTS=“${JVM_OPTS} -DIGNITE_ENABLE_EXPERIMENTAL_COMMAND=true”
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8814) Deadlock on node stop in tests
Eduard Shangareev created IGNITE-8814:
-
Summary: Deadlock on node stop in tests
Key: IGNITE-8814
URL: https://issues.apache.org/jira/browse/IGNITE-8814
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
The issue is in synchronization in IgnitionEx$IgniteNamedInstance.stop0.
I think, we should add guard and don't try to stop node again if stopping is in
progress.
{code}
"tcp-client-disco-msg-worker-#467%client%" #8733 prio=5 os_prio=0
tid=0x7fbdbe55f800 nid=0x5cd3 waiting for monitor entry [0x7fbc331ef000]
java.lang.Thread.State: BLOCKED (on object monitor)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2559)
- waiting to lock <0x00078c4e7430> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2551)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:372)
at org.apache.ignite.Ignition.stop(Ignition.java:229)
at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3404)
at
org.apache.ignite.internal.IgniteKernal.onReconnected(IgniteKernal.java:3891)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:830)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:589)
- locked <0x00078c6b81b0> (a java.lang.Object)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2423)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2402)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:2047)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1896)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1788)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{code}
{code}
"main" #1 prio=5 os_prio=0 tid=0x7fbdbc00e800 nid=0x3a56 in Object.wait()
[0x7fbdc2f19000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Thread.join(Thread.java:1252)
- locked <0x00078c4e7290> (a
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker)
at java.lang.Thread.join(Thread.java:1326)
at
org.apache.ignite.internal.util.IgniteUtils.join(IgniteUtils.java:4608)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl.spiStop(ClientImpl.java:313)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStop(TcpDiscoverySpi.java:2079)
at
org.apache.ignite.internal.managers.GridManagerAdapter.stopSpi(GridManagerAdapter.java:330)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.stop(GridDiscoveryManager.java:1675)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2191)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2069)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2588)
- locked <0x00078c4e7430> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2551)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:372)
at org.apache.ignite.Ignition.stop(Ignition.java:229)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1087)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1127)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1108)
at
org.gridgain.grid.internal.processors.cache.database.IgniteDbSnapshotNotStableTopologiesTest.afterTest(IgniteDbSnapshotNotStableTopologiesTest.java:251)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #4193: IGNITE-8806
Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/4193 ---
[GitHub] ignite pull request #3923: IGNITE-6528 Print warnings when actual data type ...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3923 ---
[jira] [Created] (IGNITE-8813) Add ComputeJobResultPolicy to JobEvent
Dmitry Karachentsev created IGNITE-8813: --- Summary: Add ComputeJobResultPolicy to JobEvent Key: IGNITE-8813 URL: https://issues.apache.org/jira/browse/IGNITE-8813 Project: Ignite Issue Type: Improvement Components: compute Affects Versions: 2.5 Reporter: Dmitry Karachentsev Assignee: Dmitry Karachentsev Fix For: 2.6 There is no way to determine on node-mapper what action would be performed on EVT_JOB_RESULTED event, as got result could return different policies: WAIT, REDUCE, FAILOVER. This knowledge might be critical for user if it relies on events, and, for instance, he need to know if EVT_JOB_RESULTED is final event, or it will be failed over and will be fired again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4210: IGNITE-8322 changed default value for preloading ...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4210 ---
Re: Separate binaries for thin clients and drivers
So, it seems, like it only has sense for ODBC Windows binaries. For Linux there are also packages that should also be used. Best Regards, Igor On Mon, Jun 18, 2018 at 10:04 AM Pavel Tupitsyn wrote: > Same thing with package manager for .NET (NuGet). > And same with Java, actually (Maven). > > In my understanding, most people use package managers and don't download > ZIP archives. > Package managers are more convenient and easy to use. It is a modern way. > > > On Sun, Jun 17, 2018 at 11:28 AM, Aleksandr Sokolovskii > > wrote: > > > Hi All, > > > > The same situation is for Go lang also. > > There are no binaries. > > Libraries are installed from source code repo, etc.: > > > > go get -u github.com/amsokol/ignite-go-client > > > > So the proposal is not really applicable to Go lang client. > > > > Thanks, > > Aleksandr > > > > From: Pavel Petroshenko > > Sent: 16 июня 2018 г. 21:10 > > To: Denis Magda > > Cc: dev > > Subject: Re: Separate binaries for thin clients and drivers > > > > Hi Denis, > > > > There are no "binaries" for Node.js and Python that you can download. > These > > Thin Clients are distributed and installed by a package management system > > (npm, pip): which resolves all the dependencies and deploys necessary > > components to the appropriate system locations. So instead of > downloading a > > Node or Python package binary, the package management systems should be > > used to properly install it: > > > > Node.js: $ npm install <...> > > or > > Python: $ pip install <...> > > > > So the proposal is not really applicable to these clients. > > > > Pavel > > > > > > > > On Sat, Jun 16, 2018 at 12:45 AM, Dmitriy Setrakyan < > dsetrak...@apache.org > > > > > wrote: > > > > > +1 > > > > > > On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda > wrote: > > > > > > > Igniters, > > > > > > > > Presently, all our thin clients and SQL drivers are stored in the > main > > > > Ignite repository. That's totally fine, I wouldn't change anything in > > > here. > > > > > > > > But, what I would encourage us to contemplate on is how a user gets > and > > > > downloads those binaries. Basically, the user has to download the > whole > > > > Ignite distribution even if he needs just a JDBC driver or Node.JS > thin > > > > driver. > > > > > > > > The proposal is pretty simple. In addition to the main distribution, > > > let's > > > > prepare separate ZIP archives with binaries for: > > > > > > > >- JDBC > > > >- ODBC > > > >- Thin clients (Java, C#, Node.JS, Python, etc.) > > > > > > > > The binaries would be available for downloads on the main page: > > > > https://ignite.apache.org/download.cgi > > > > > > > > Thoughts? Supporters and opposers, please speak out. > > > > > > > > -- > > > > Denis > > > > > > > > > > > >
[GitHub] ignite pull request #4210: IGNITE-8322 changed default value for preloading ...
GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/4210 IGNITE-8322 changed default value for preloading option to 'false' You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8322-fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4210.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4210 commit b6037c37cdc34ca8f964b7af30835b2474ca9db2 Author: oleg-ostanin Date: 2018-06-18T07:17:36Z IGNITE-8322 changed default value for preloading option to 'false' ---
Re: Separate binaries for thin clients and drivers
Same thing with package manager for .NET (NuGet). And same with Java, actually (Maven). In my understanding, most people use package managers and don't download ZIP archives. Package managers are more convenient and easy to use. It is a modern way. On Sun, Jun 17, 2018 at 11:28 AM, Aleksandr Sokolovskii wrote: > Hi All, > > The same situation is for Go lang also. > There are no binaries. > Libraries are installed from source code repo, etc.: > > go get -u github.com/amsokol/ignite-go-client > > So the proposal is not really applicable to Go lang client. > > Thanks, > Aleksandr > > From: Pavel Petroshenko > Sent: 16 июня 2018 г. 21:10 > To: Denis Magda > Cc: dev > Subject: Re: Separate binaries for thin clients and drivers > > Hi Denis, > > There are no "binaries" for Node.js and Python that you can download. These > Thin Clients are distributed and installed by a package management system > (npm, pip): which resolves all the dependencies and deploys necessary > components to the appropriate system locations. So instead of downloading a > Node or Python package binary, the package management systems should be > used to properly install it: > > Node.js: $ npm install <...> > or > Python: $ pip install <...> > > So the proposal is not really applicable to these clients. > > Pavel > > > > On Sat, Jun 16, 2018 at 12:45 AM, Dmitriy Setrakyan > > wrote: > > > +1 > > > > On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda wrote: > > > > > Igniters, > > > > > > Presently, all our thin clients and SQL drivers are stored in the main > > > Ignite repository. That's totally fine, I wouldn't change anything in > > here. > > > > > > But, what I would encourage us to contemplate on is how a user gets and > > > downloads those binaries. Basically, the user has to download the whole > > > Ignite distribution even if he needs just a JDBC driver or Node.JS thin > > > driver. > > > > > > The proposal is pretty simple. In addition to the main distribution, > > let's > > > prepare separate ZIP archives with binaries for: > > > > > >- JDBC > > >- ODBC > > >- Thin clients (Java, C#, Node.JS, Python, etc.) > > > > > > The binaries would be available for downloads on the main page: > > > https://ignite.apache.org/download.cgi > > > > > > Thoughts? Supporters and opposers, please speak out. > > > > > > -- > > > Denis > > > > > > >
