[jira] [Created] (IGNITE-9470) MVCC TX: Mvcc transactions should throw proper exception when rolled back.
Roman Kondakov created IGNITE-9470:
--
Summary: MVCC TX: Mvcc transactions should throw proper exception
when rolled back.
Key: IGNITE-9470
URL: https://issues.apache.org/jira/browse/IGNITE-9470
Project: Ignite
Issue Type: Bug
Components: jdbc, mvcc, odbc
Reporter: Roman Kondakov
Fix For: 2.7
When MVCC transaction is rolled back due to a write conflict it throws
{{CacheException}} with "Mvcc version mismatch" message. This behavior violates
Ignite transactions API. Instead it should throw
{{TransactionRollbackException}} with a clear message like a "Transaction has
been aborted due to a write conflict (Please try again.)"
It is also need to propogate this changes to JDBC and ODBC components and fix
mvcc tests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9471) Failed to validate indexes by control.sh utility.
Dmitriy Gladkikh created IGNITE-9471:
Summary: Failed to validate indexes by control.sh utility.
Key: IGNITE-9471
URL: https://issues.apache.org/jira/browse/IGNITE-9471
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5
Reporter: Dmitriy Gladkikh
During the validation of the indexes, an error occurs:
{noformat}
2018-08-31 17:18:40.356 [WARN
][pool-19-thread-1][o.a.i.i.v.v.ValidateIndexesClosure] Current progress of
ValidateIndexesClosure: processed 0 of 0 partitions, 0 of 0 SQL indexes
2018-08-31 17:18:40.625
[ERROR][pool-19-thread-1][o.a.i.i.v.v.ValidateIndexesClosure] Failed to invoke
typeByValue
java.lang.NullPointerException: null
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.typeByValue(GridQueryProcessor.java:1901)
at sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.ignite.internal.visor.verify.ValidateIndexesClosure.processPartition(ValidateIndexesClosure.java:375)
at
org.apache.ignite.internal.visor.verify.ValidateIndexesClosure.access$000(ValidateIndexesClosure.java:77)
at
org.apache.ignite.internal.visor.verify.ValidateIndexesClosure$1.call(ValidateIndexesClosure.java:282)
at
org.apache.ignite.internal.visor.verify.ValidateIndexesClosure$1.call(ValidateIndexesClosure.java:280)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
2018-08-31 17:18:40.638
[ERROR][mgmt-#717%DPL_GRID%DplGridNodeName%][o.a.i.i.processors.job.GridJobWorker]
Failed to execute job [jobId=1ebe4309561-6878f409-b4fd-4f51-9f74-5f5c2241059a,
ses=GridJobSessionImpl [ses=GridTaskSessionImpl
[taskName=o.a.i.i.v.verify.VisorValidateIndexesTask, dep=GridDeployment
[ts=1535721804597, depMode=SHARED,
clsLdr=union-module-impl:com.sbt.core.envelope.container.loader.ImplClassLoader@1b1d1738,
clsLdrId=b3ac6209561-64663e4a-48d0-468f-999f-ade455ad6a4a, userVer=0,
loc=true, sampleClsName=o.a.i.i.v.misc.VisorResolveHostNameTask,
pendingUndeploy=false, undeployed=false, usage=1],
taskClsName=o.a.i.i.v.verify.VisorValidateIndexesTask,
sesId=edbe4309561-6878f409-b4fd-4f51-9f74-5f5c2241059a,
startTime=1535725120340, endTime=9223372036854775807,
taskNodeId=6878f409-b4fd-4f51-9f74-5f5c2241059a,
clsLdr=union-module-impl:com.sbt.core.envelope.container.loader.ImplClassLoader@1b1d1738,
closed=false, cpSpi=null, failSpi=null, loadSpi=null, usage=1, fullSup=false,
internal=true, topPred=null, subjId=6878f409-b4fd-4f51-9f74-5f5c2241059a,
mapFut=IgniteFuture [orig=GridFutureAdapter [ignoreInterrupts=false,
state=INIT, res=null, hash=2010820403]], execName=null],
jobId=1ebe4309561-6878f409-b4fd-4f51-9f74-5f5c2241059a]]
org.apache.ignite.IgniteException: null
at
org.apache.ignite.internal.visor.verify.VisorValidateIndexesTask$VisorValidateIndexesJob.run(VisorValidateIndexesTask.java:86)
at
org.apache.ignite.internal.visor.verify.VisorValidateIndexesTask$VisorValidateIndexesJob.run(VisorValidateIndexesTask.java:64)
at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6695)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
at
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1921)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
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)
[GitHub] ignite pull request #4650: IGNITE-9408: Update Apache Mesos version.
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4650 ---
Re: [ML] PR for ml-starter task IGNITE-9285
Yes, I reviewed this ticket and it could be merged immediately. 5 сент. 2018 г. 9:30 AM пользователь "Ravil Galeyev" написал: > Hi team, > > Could @ybabak or someone, merge my PR > https://github.com/apache/ignite/pull/4655 > for task https://issues.apache.org/jira/browse/IGNITE-9285 > > @zaleslaw has already reviewed it. > > Best regards, > Ravil >
[GitHub] ignite pull request #4682: IGNITE-6454 muted flaky tests
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4682 ---
[GitHub] ignite pull request #4684: IGNITE-9298
GitHub user deviljelly opened a pull request: https://github.com/apache/ignite/pull/4684 IGNITE-9298 Adds support for SSL to CommandHandler (control.sh) You can merge this pull request into a Git repository by running: $ git pull https://github.com/deviljelly/ignite ignite-9298 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4684.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 #4684 commit 2958693de4e98ccd1bbb67033ed61b494f3b0030 Author: deviljelly Date: 2018-08-19T14:06:56Z Learning git commit 025e0259724e93491882039c98babde3f994eaa1 Author: deviljelly Date: 2018-08-19T14:28:01Z Initial commit to support SSL in CommandHandler (control.sh) commit 8a5b79888bf2888453a332a2377415afaf889cf7 Author: deviljelly Date: 2018-09-05T08:27:35Z Add SSL argument tests commit ed1970b40a354cbfbe7c56e711d0f30b22960c53 Author: deviljelly Date: 2018-09-05T08:35:50Z Fix comment ---
[GitHub] ignite pull request #4658: IGNITE-9438 fix standaloneWalRecordsIterator file...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4658 ---
Re: Compression prototype
Hello! Of course, this setting will be configurable. Regards, -- Ilya Kasnacheev ср, 5 сент. 2018 г. в 3:21, Dmitriy Setrakyan : > In my view, dictionary of 1024 bytes is not going to be nearly enough. > > On Tue, Sep 4, 2018 at 8:06 AM, Ilya Kasnacheev > > wrote: > > > Hello! > > > > In case of Apache Ignite, most of savings is due to BinaryObject format, > > which encodes types and fields with byte sequences. Any enum/string flags > > will also get in dictionary. And then as it processes a record it fills > up > > its individual dictionary. > > > > But, in one cache, most if not all entries have identical BinaryObject > > layout so a tiny dictionary covers that case. Compression algorithms are > > not very keen on large dictionaries, preferring to work with local > > regularities in byte stream. > > > > E.g. if we have large entries in cache with low BinaryObject overhead, > > they're served just fine by "generic" compression. > > > > All of the above is my speculations, actually. I just observe that on a > > large data set, compression ratio is around 0.4 (2.5x) with a dictionary > of > > 1024 bytes. The rest is black box. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > вт, 4 сент. 2018 г. в 17:16, Dmitriy Setrakyan : > > > > > On Tue, Sep 4, 2018 at 2:55 AM, Ilya Kasnacheev < > > ilya.kasnach...@gmail.com > > > > > > > wrote: > > > > > > > Hello! > > > > > > > > Each node has a local dictionary (per node currently, per cache > > planned). > > > > Dictionary is never shared between nodes. As data patterns shift, > > > > dictionary rotation is also planned. > > > > > > > > With Zstd, the best dictionary size seems to be 1024 bytes. I imagine > > It > > > is > > > > enough to store common BinaryObject boilerplate, and everything else > is > > > > compressed on the fly. The source sample is 16k records. > > > > > > > > > > > Thanks, Ilya, understood. I think per-cache is a better idea. However, > I > > > have a question about dictionary size. Ignite stores TBs of data. How > do > > > you plan the dictionary to fit in 1K bytes? > > > > > > D. > > > > > >
[GitHub] ignite pull request #4685: IGNITE-4111
GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/4685 IGNITE-4111 Fix for IGNITE-4111 Communication fails to send message if target node did not finish join process You can merge this pull request into a Git repository by running: $ git pull https://github.com/NSAmelchev/ignite ignite-4111 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4685.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 #4685 commit bfb00b6e61f9709718c30971997aeb0ac79e86b4 Author: Alexandr Kuramshin Date: 2016-11-18T20:12:28Z IgniteTcpCommunicationBigClusterTest added commit 02dd92e605b9b53f5a16c7ec5f8e7b5698b15ba4 Author: Alexandr Kuramshin Date: 2016-11-18T21:55:37Z IgniteTcpCommunicationBigClusterTest update commit 6acf193a3d356d1bad4c02a53ac76833ed1008d0 Author: Alexandr Kuramshin Date: 2016-11-19T09:55:45Z Have got TcpCommunicationSpi error commit 4fd39653d24f62f19f70b4dffba8497185cc46fb Author: Alexandr Kuramshin Date: 2016-11-19T16:39:10Z Some discovery have been done commit c2c181922c7c24ea457577e32d2af897c8bec87f Author: Alexandr Kuramshin Date: 2016-11-19T20:11:28Z Prove that problem is not in the onFirstMessage hang commit f8076edba097f6077229b2090ee3ff1a3369878c Author: Alexandr Kuramshin Date: 2016-11-19T20:26:37Z Revert: Prove that problem is not in the onFirstMessage hang commit 9415f11564480ae61952b7ad551518141b5ad7c0 Author: Alexandr Kuramshin Date: 2016-11-19T20:55:15Z Prove that problem is not in the onFirstMessage hang commit dc95254a8030f03e485fe535bb286eb1a7b99f63 Author: Alexandr Kuramshin Date: 2016-11-21T08:51:26Z Hang dectection commit 6e1f2dfc2acb3dbb8f24aa51ed67b2ee447b4585 Author: Alexandr Kuramshin Date: 2016-11-21T08:55:09Z Revert: pushing unnecessary changes to the master commit ed794ca815f6bb1471af15779279d287576b39cc Author: Alexandr Kuramshin Date: 2016-11-21T09:08:00Z Revert: pushing unnecessary changes to the master commit bcd049d09dadb20295eb87667d20101d7fb41790 Author: Alexandr Kuramshin Date: 2016-11-21T19:45:10Z Fix: get handshake error on long delivery addNodeFinished message commit a33f22a9da972b769bf63de04f86b42741c7f0d6 Author: Alexandr Kuramshin Date: 2016-11-22T10:39:04Z Include the test into Communication SPI Test Suite commit f8ba785e43993639e30e8e048def5533eefedc32 Author: Alexandr Kuramshin Date: 2016-11-22T10:50:03Z Removing unnecessary changes commit 7bc8ac878a5761fc111d7e5e71222a8cef4335d7 Author: Alexandr Kuramshin Date: 2016-11-22T10:54:06Z Removing unnecessary changes commit fb95a5af0f43f3c1a0ebb4f375280225bec5ec98 Author: Alexandr Kuramshin Date: 2016-11-22T12:55:19Z java7 syntax commit dc2814a2beaa53761329654f52d669fc4f0cc7c7 Author: Alexandr Kuramshin Date: 2016-11-25T11:20:13Z fix INIT_TIMEOUT_MSG_TYPE = -28 fix message codes comment commit b10a57c1073bd0305748af46bd9b787c7b283ff0 Author: Alexandr Kuramshin Date: 2016-11-28T11:07:02Z add license header commit 8ed19a042a8c0e9e061e3c286635b1e9521f1047 Author: Alexandr Kuramshin Date: 2016-12-01T13:03:28Z Merge remote-tracking branch 'remotes/origin/master' into ignite-4111 commit eca325b9bc96426aa4ddc44169df89ee26b9453b Author: Alexandr Kuramshin Date: 2016-12-01T13:15:07Z Merge remote-tracking branch 'remotes/apache/master' into ignite-4111 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/managers/communication/GridIoMessageFactory.java commit eeaf5bc95dc50b506dc531e919f806f271761cc6 Author: NSAmelchev Date: 2018-09-04T14:22:54Z Merge commit 'refs/pull/1307/head' of https://github.com/apache/ignite into ignite-4111 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/managers/communication/GridIoMessageFactory.java # modules/core/src/main/java/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.java commit 0154877f927eba6ebd96dee2942b9572017499f9 Author: NSAmelchev Date: 2018-09-04T14:28:16Z fixed build after merge ---
[jira] [Created] (IGNITE-9472) REST API has no permission checks for cluster activation/deactivation
Ivan Bessonov created IGNITE-9472: - Summary: REST API has no permission checks for cluster activation/deactivation Key: IGNITE-9472 URL: https://issues.apache.org/jira/browse/IGNITE-9472 Project: Ignite Issue Type: Bug Reporter: Ivan Bessonov Assignee: Ivan Bessonov ADMIN_OPS permission should be required for CLUSTER_ACTIVE / CLUSTER_INACTIVE commands. This has to be done in GridRestProcessor.authorize method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: IGNITE-640: multimap initial implementation
Denis, Discussion relocated to the issue. Amir is working on implementation now. ср, 5 сент. 2018 г. в 1:53, Denis Magda : > Amir, Anton, > > How is dev/review process going? Is there any chance we get this capability > into 2.7? > > -- > Denis > > On Mon, Jul 9, 2018 at 10:27 PM Amir Akhmedov > wrote: > > > Hi Anton, > > > > I checked your last comments in the ticket and left some responses. > Please > > check them and let me know > > > > Thanks, > > Amir > > > > P.S. do you mind to have a chat/call through gitter/Skype to discuss the > > details? Sometimes 5 minutes of chat can be more productive than long > > running email chains. Please, do not hesitate to directly email me if you > > mind to have a chat/call. > > > > On Wed, Jun 27, 2018 at 11:26 AM Anton Vinogradov wrote: > > > > > Sure, > > > Hope it will be tomorrow > > > > > > ср, 27 июн. 2018 г. в 18:11, Amir Akhmedov : > > > > > > > Anton V, > > > > I put some comments into jira ticket. Can you please take a look once > > you > > > > have a chance? > > > > > > > > Thanks, > > > > Amir > > > > > > > > On Mon, Jun 18, 2018, 7:54 AM Anton Vinogradov > wrote: > > > > > > > > > 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 < > > amir.akhme...@gmail.com > > > >: > > > > > > > > > > > > > > > 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 < > > > > > dpavlov@gmail.com > > > > > > > > > > > > > > > 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 < > > > dpavlov@gmail.com > > > > >: > > > > > > > > > > > > > > > > > > > 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 < > > > > amir.akhme...@gmail.com > > > > > >: > > > > > > > > > > > > > > > > > > > >> 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: > > > > > > > > > >
[GitHub] ignite pull request #4686: IGNITE-9472 Added permissions check on cluster ac...
GitHub user ibessonov opened a pull request: https://github.com/apache/ignite/pull/4686 IGNITE-9472 Added permissions check on cluster activation You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9472 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4686.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 #4686 commit 7e1adaafb807dfc4fe5b747e484bab88c4d93bfd Author: ibessonov Date: 2018-09-05T09:08:43Z IGNITE-9472 Added permissions check on cluster activation ---
Re: Hi... trying to write a test case for a pacth ... need help....
Hello! 1) It is really advised to run tests from IDEA (that's what absolute majority of active contributors seem to be using), but you can also run it with mvn clean install -Dtest=SimpleClassNameOfTest -DfailIfNoTests=false 2) enable 'examples' profile and run ExampleNodeStartup class. Regards, -- Ilya Kasnacheev вт, 4 сент. 2018 г. в 16:57, Paul Anderson : > ... The code is done ready to go, but the test suite looks huge, I know the > two test classes I have to augment... but I am unsure of a couple of > things. > > 1) how do I run a specific test (command line) > 2) how do I start (make sure is started) an ignite instance >
[jira] [Created] (IGNITE-9473) InvalidPathException when localizing resources for Tez job
Rob Gibbon created IGNITE-9473:
--
Summary: InvalidPathException when localizing resources for Tez job
Key: IGNITE-9473
URL: https://issues.apache.org/jira/browse/IGNITE-9473
Project: Ignite
Issue Type: Bug
Components: igfs
Affects Versions: 2.6
Environment: Hadoop 3.1.1
Ignite 2.6
Reporter: Rob Gibbon
When running a Hive on Tez job with an IGFS backend, I get an error:
InvalidPathException: Invalid path name Wrong path authority [expected=igfs@,
actual=null]
The path is interpreted by the Yarn resource localizer as
igfs:/apps/tez/tez.tar.gz.
The path is configured in tez.lib.uris as /apps/tez/tez.tar.gz
The defaultFS is configured as igfs://igfs@/
The system works for everything else.
exact error message logged:
localizer.ResourceLocalizationService: Failed to download resource \{ {
igfs:/apps/tez/tez.tar.gz, 1536087125000, ARCHIVE, null
},pending,[(container_1536139312517_0016_01_01)],592502389438828,DOWNLOADING}
Need help with this...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #4640: IGNITE-9402
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4640 ---
[GitHub] ignite pull request #4464: IGNITE-8158 Wrap the method afterTestsStopped() c...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4464 ---
[jira] [Created] (IGNITE-9474) Ignite does not eagerly remove expired cache entries
Pavel Vinokurov created IGNITE-9474: --- Summary: Ignite does not eagerly remove expired cache entries Key: IGNITE-9474 URL: https://issues.apache.org/jira/browse/IGNITE-9474 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.4 Reporter: Pavel Vinokurov Attachments: IgniteExpirationReproducerWithoutPersistance.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9475) Closures that has been created on client does not provide real class name to TASK_* permissions
Ivan Bessonov created IGNITE-9475:
-
Summary: Closures that has been created on client does not provide
real class name to TASK_* permissions
Key: IGNITE-9475
URL: https://issues.apache.org/jira/browse/IGNITE-9475
Project: Ignite
Issue Type: Bug
Reporter: Ivan Bessonov
Assignee: Ivan Bessonov
Broadcast job for example get
org.apache.ignite.internal.processors.closure.GridClosureProcessor$T6 task name.
This combination of java + xml config
{code:java}
ignite.compute(ignite.cluster().forServers()).broadcast(new
DistributedJob(cacheName));
{code}
{code:java}
{
task:'org.apache.ignite.piclient.operations.DistributedChecksumOperation$DistributedJob',
permissions:[TASK_EXECUTE]
},
{code}
provides following error
{code:java}
Authorization failed [perm=TASK_EXECUTE,
name=org.apache.ignite.internal.processors.closure.GridClosureProcessor$T6, ...
]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #4687: Revert TOPIC_MONGO removal in "IGNITE-9361 Remove...
GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/4687 Revert TOPIC_MONGO removal in "IGNITE-9361 Remove IgniteInternalCache⦠â¦.isMongo*Cache() and other remnants." This partially reverts commit de30a86e740067ed239602fb5dc28396144fd446. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9361-bis Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4687.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 #4687 commit 4f2cf3f6d38203957324b9e5eb40c826355a59e1 Author: Ilya Kasnacheev Date: 2018-09-05T12:42:26Z Revert TOPIC_MONGO removal in "IGNITE-9361 Remove IgniteInternalCache.isMongo*Cache() and other remnants." This partially reverts commit de30a86e740067ed239602fb5dc28396144fd446. ---
[GitHub] ignite pull request #4688: IGNITE-9475 Use proper task class name for the er...
GitHub user ibessonov opened a pull request: https://github.com/apache/ignite/pull/4688 IGNITE-9475 Use proper task class name for the error message You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9475 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4688.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 #4688 commit f394e19b55d4e1be47ac65f0fa313d01b8abc1cd Author: ibessonov Date: 2018-09-05T13:46:21Z IGNITE-9475 Use proper task class name for the error message ---
[GitHub] ignite pull request #4689: IGNITE-8331 Add Decimal precision and scale const...
GitHub user ololo3000 opened a pull request: https://github.com/apache/ignite/pull/4689 IGNITE-8331 Add Decimal precision and scale constraint You can merge this pull request into a Git repository by running: $ git pull https://github.com/ololo3000/ignite IGNITE-8331 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4689.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 #4689 commit 960a63b571ab1d56b711e419c5960f2be4755db8 Author: ololo3000 Date: 2018-09-05T12:29:18Z IGNITE-8331 Add Decimal precision and scale constraint ---
[GitHub] ignite pull request #4687: Revert TOPIC_MONGO removal in "IGNITE-9361 Remove...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4687 ---
Minor version changes and server/client compatibility
We have needed to do a couple of simple bug fixes to ignite proper, where there is no change to interfaces or internode communications. When we do this, we end up with these choices: - Coordinate client and server code bases so that they are in lock step. Tedious with multiple clusters and test/dev versions. - Force the prior version number on the new builds, making it more tedious to understand what versions we are running. A standard practice would to ignore the last field in the version when doing a compatibility test, e.g., 2.5.0 and 2.5.foobar would be considered compatible.Is there some reason ignite requires and exact match? How do other Ignite users handle this problem? Thanks, -DH
[GitHub] ignite pull request #4690: Ignite 2.5.1 p12 notrace
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/4690 Ignite 2.5.1 p12 notrace You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p12-notrace Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4690.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 #4690 commit b3f252666785fddf41ef07846e034d55ae0dda71 Author: Alexey Kukushkin Date: 2018-04-16T08:47:19Z IGNITE-8097: Java thin client: throw handshake exception eagerly on connect phase in case of failure. This closes #3822. commit 7173b0c48dab05be0b8e7825ae527824fcdbbc83 Author: zaleslaw Date: 2018-04-16T17:20:49Z IGNITE-8169: [ML] Adopt KMeans to the new Partitioned Dataset and cleanup old code this closes #3817 (cherry picked from commit 9e21cec) commit 6ee5e9fe8c07353a55a2a02b84f7b94c43b5c49f Author: Alexey Kuznetsov Date: 2018-04-17T04:46:45Z IGNITE-8201 REST: Added AUTHENTICATE command. Fixed session tokens. Added new tests. (cherry picked from commit 1cfc989) commit 7457fd319a372d54de68271be7fddbb634cb6070 Author: Anton Kalashnikov Date: 2018-04-17T07:30:52Z IGNITE-8048 Store dynamic indexes to cache data on node join - Fixes #3719. Signed-off-by: Alexey Goncharuk commit 2883ff4e958747916e7d9eec671100c366cad66b Author: Ilya Borisov Date: 2018-04-17T08:01:36Z IGNITE-8291 Web Console: Fixed Docker file generation. (cherry picked from commit 5614621) commit d0997d7740ea1114b4c8236f225d989de98e2f10 Author: YuriBabak Date: 2018-04-17T08:22:14Z IGNITE-8292: Broken yardstick compilation. this closes #3838 (cherry picked from commit e76fcb4) commit 3d2556bc73eff6c5ccd52af1bea88b6016358db8 Author: Ilya Borisov Date: 2018-04-17T08:46:10Z IGNITE-8285 Web console: Removed debug output. (cherry picked from commit 8c80dce) commit 4846e967e4cb7a174880a2956e807505a78fd441 Author: YuriBabak Date: 2018-04-17T08:54:41Z IGNITE-8292: Broken yardstick compilation. this closes #3840 (cherry picked from commit 3cebf91) commit 733a62bcb6c0d9381a496f07417c10c7edea6d7c Author: Ilya Borisov Date: 2018-04-17T07:12:39Z IGNITE-8287 Change position on signup inputs on page-sign-in. (cherry picked from commit e5c3f89) commit 83e54311fce1d46279c6ddd687ced6f7c9f17ff6 Author: Ilya Borisov Date: 2018-04-17T10:15:57Z IGNITE-8200 Web Console: Override clonedCluster in cluster-edit-form if caches or models have changed. This improves interop with "import from DB" feature, which might update caches/models of cluster currently opened for editing. The import dialog works as a separate state, so the form change detection mechanism ensures that any changes to the original cluster are safe and won't interfere with changes made by user in cluster edit form. (cherry picked from commit 7731669) commit 86d3f196e436095f277bb9b3e2c32293185db634 Author: Sergey Chugunov Date: 2018-04-17T11:28:47Z IGNITE-8210 Fixed custom event handling for baseline topology change - Fixes #3814. Signed-off-by: Alexey Goncharuk commit a7dbea16064bbd52907a770bb40c3a2445313db2 Author: Dmitriy Sorokin Date: 2018-04-17T11:48:44Z IGNITE-8255 Possible name collisions in WorkersRegistry. Signed-off-by: Andrey Gura commit b762d681b97ea121a8321eb66bf02f89a1d177cd Author: Aleksey Plekhanov Date: 2018-04-17T12:56:36Z IGNITE-8166 PME hangs when error occurs during checkpoint Signed-off-by: Andrey Gura commit 8428b0e63e97c10277f6d9e1640e16528a772270 Author: Ivan Daschinskiy Date: 2018-04-17T15:05:42Z IGNITE-8021 Delete cache config files when cache is destroyed - Fixes #3697. Signed-off-by: Alexey Goncharuk commit cd59c8e64f05ca03c7da8dc35d027a14fcebf250 Author: Aleksey Plekhanov Date: 2018-04-17T15:27:53Z IGNITE-8033 Fixed flaky failure of TxOptimisticDeadlockDetectionCrossCacheTest Signed-off-by: Andrey Gura commit acfef907db8204ac93fc235770f36bf7f61269c3 Author: Ilya Kasnacheev Date: 2018-04-17T16:50:51Z IGNITE-2766 Fix .net test. - Fixes #3853. Signed-off-by: dpavlov (cherry picked from commit 96cb795) commit 6cea78e4e13fe43555b78dcd683366f54c6816ff Author: Andrey Kuznetsov Date: 2018-04-17T16:58:43Z IGNITE-7770 Test testRandomMixedTxConfigurations partialy fixed Signed-off-by: Andrey Gura commit e394693a7389b4daff328827abdb1dcd28783f66 Author: Maxim Muzafarov Date: 2018-04-17T18:18:36Z IGNITE-8301 testReconnectCacheDestroyedAndCreated should excpect recreated client cache - Fixes #3856. Signed-off-by: dpavlov (cherry picked from com
Re: Thin Client lib: Python
Hi Dmitry M,
Is the API Specification [1] section of the documentation auto-generated
from the code?
[1]
https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/modules.html
On Mon, Jul 30, 2018 at 5:05 PM, Dmitriy Setrakyan
wrote:
> Now we are talking. A much better and more user-friendly API.
>
> D.
>
> On Fri, Jul 27, 2018 at 7:19 AM, Dmitry Melnichuk <
> dmitry.melnic...@nobitlost.com> wrote:
>
> > Dmitriy, Igor, Ilya, Sergey!
> >
> > Thank you for sharing your ideas, concerns and criticism with me. I do
> > appreciate it.
> >
> > I already made some changes in my API, influenced by your feedback. I
> also
> > plan to add a certain set of features, that will make my UX closer to
> what
> > you can see from other Ignite clients.
> >
> > I stopped using `hashcode` in my examples. Integer cache IDs and cache
> > names now can be used interchangeably, with primary focus on cache names.
> >
> > I will add a Cache class as a primary interface for cache operations, so
> > that earlier examples:
> >
> > ```
> > conn = Connection()
> > conn.connect('127.0.0.1', 10800)
> >
> > cache_create(conn, 'my cache')
> >
> > cache_put(conn, 'my cache', 'my key', 42)
> > result = my_cache.get('my key')
> >
> > cache_destroy(conn, 'my cache')
> > conn.close()
> > ```
> >
> > could be reiterated as:
> >
> > ```
> > conn = Connection()
> > conn.connect('127.0.0.1', 10800)
> >
> > my_cache = conn.create_cache('my cache')
> >
> > my_cache.put('my key', 42)
> > result = my_cache.get('my key')
> >
> > my_cache.destroy('my cache')
> > conn.close()
> > ```
> >
> > I will also make `Connection.connect()` accept any iterable (including
> > simple list) as a connection parameter. I will provide user with some
> basic
> > connection generators instead of what is done in my current connection
> > failover example.
> >
> >
> > On 07/27/2018 07:41 AM, Dmitriy Setrakyan wrote:
> >
> >> Dmitriy,
> >>
> >> I would stop using the word "hashcode" in this context. Hash code has a
> >> special meaning in Ignite and is used to determine key-to-node
> affinity. I
> >> agree that passing "cache_name" is the best option. I have no idea when
> >> "cache_name" is not going to be known and do not think we need to
> support
> >> this case at all. My suggestion is to drop the cache_id use case
> >> altogether.
> >>
> >> Also I am really surprised that we do not have a cache abstraction in
> >> python and need to pass cache name and connection into every method. To
> be
> >> honest, this smells really bad that such a popular modern language like
> >> Python forces us to have such a clumsy API. Can you please take a look
> at
> >> the Redis python clients and see if there is a better way to support
> this?
> >>
> >> https://redis.io/clients#python
> >>
> >> D.
> >>
> >
>
[jira] [Created] (IGNITE-9476) Web console: extract configuration-specific mixins from mixins.pug
Ilya Borisov created IGNITE-9476: Summary: Web console: extract configuration-specific mixins from mixins.pug Key: IGNITE-9476 URL: https://issues.apache.org/jira/browse/IGNITE-9476 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Ilya Borisov Assignee: Alexander Kalinin Most of form field Pug mixins used in configuration are very specific to it and are not used elsewhere. The _mixins.pug_ that these currently reside in is too big for my liking. I suggest to move all configuration mixins to configuration module (for example, _page-configure/mixins.pug_), with the following benefits: # All code specific to configuration will stay in configuration module. # mixins.pug will become easier to maintain. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Thin Client lib: Python
Hello, Prachi! The section is a hand-written .rst-file, which contains links to some content, generated from code with `sphinx-apidoc`. All autogenerated content resides in `source` folder. For example, this is an autogenerated page: https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/source/pyignite.client.html And this is written by hand: https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/datatypes/parsers.html On 9/6/18 9:39 AM, Prachi Garg wrote: Hi Dmitry M, Is the API Specification [1] section of the documentation auto-generated from the code? [1] https://apache-ignite-binary-protocol-client.readthedocs.io/en/latest/modules.html
