Re: How to fix documents?
Hi, Got it. And my change has been accepted. Thank you. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
.NET - Complex LINQ queries support
Hi Team, Is there any plan to support LINQ queries like: var result = cache.AsCacheQueryable .Where(entry => !entry.Value.Dirty.HasValue) .GroupBy(entry => entry.Value.ContractId) .Select(group => group.OrderByDescending(entry => entry.Value.Version).First().Key) .ToList(); It looks like such queries need be transformed to complex SQL like `SELECT ... FROM (SELECT ... FROM (SELECT ...) JOIN ...)`. And probably that's why it's not easy to implement such functionality, but users quite often want to use that. Will it be implemented in the near future? Is there any ticket for that? Thanks. Best Regards, Roman -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
[GitHub] ignite pull request #4233: Revert 1 master
GitHub user kcmvp opened a pull request: https://github.com/apache/ignite/pull/4233 Revert 1 master You can merge this pull request into a Git repository by running: $ git pull https://github.com/kcmvp/ignite revert-1-master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4233.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 #4233 commit 66865729c1d964de3e363155bfab240d976c237c Author: kcmvp Date: 2018-06-21T01:31:34Z Merge pull request #1 from apache/master Update from upstream repo apache/ignite@master commit bfe9eebf13c3255ff7301327326f13517df3604d Author: kcmvp Date: 2018-06-21T01:35:33Z Revert "Update from upstream repo apache/ignite@master" ---
[GitHub] ignite pull request #4233: Revert 1 master
Github user kcmvp closed the pull request at: https://github.com/apache/ignite/pull/4233 ---
[jira] [Created] (IGNITE-8841) MVCC TX: Read transactions remap when coordinator fails.
Roman Kondakov created IGNITE-8841: -- Summary: MVCC TX: Read transactions remap when coordinator fails. Key: IGNITE-8841 URL: https://issues.apache.org/jira/browse/IGNITE-8841 Project: Ignite Issue Type: Improvement Components: sql Reporter: Roman Kondakov At the moment all read transactions are forcibly rolled back during coordinator change. It would be nice to remap it somehow until they locked a topology. For example, it is possible to obtain a new "write" mvcc version from the new coordinator and use this version for all further writes while using "old" version for reads. In this case we need to change visibility rules a little: "old" version should see "own" updates made by "new" "write" version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Contribuition request: Random Forest
Hello Alexey and welcome! Added you to JIRA. Look forward to your contributions! Feel free to ask any questions. -- Denis On Wed, Jun 20, 2018 at 8:23 AM aplatonov wrote: > Hello, my name is Alexey Platonov. My Jira-id = aplatonov. > I want to work on task IGNITE-8840. So please give me permissions for task > assignment. > Thanks. > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >
Re: How to fix documents?
Hi, It makes sense to create a ticket for significant improvements or if you just don't want to submit edits on your own but spotted an issue. If you have time to improve the doc, you can submit your edits via readme.io. We receive notifications for every submission. Is there a chance we've accepted your changes? If don't, please try to submit once again just to confirm the functionality works. -- Denis On Tue, Jun 19, 2018 at 7:57 PM Hu Hailin wrote: > Hi, > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document > I have read the how-to. > > And my question is, is a JIRA ticket required for document-only fix? For > example, to fix a broken link. > > https://apacheignite.readme.io/docs/memcached-support > Recently I just submitted a SUGGEST EDITS to fix the not-work ruby example > code. But nothing like auto-reply or edit history anywhere, I guess the way > I did doesn't work. > > Thanks. > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >
[GitHub] ignite pull request #4228: IGNITE-8838: Fixed issue with two inserts without...
Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/4228 ---
Enabling Persistent Memory for Ignite
Hi, We have shared an experimental patch that optionally enables a 3DXPoint (aka Intel Optane DC Persistent Memory) persistent store for Ignite. The work is still in progress we welcome your code review and feedback. The patch is based on a Low Level Persistent Library (LLPL) we released earlier. Jira: https://issues.apache.org/jira/browse/IGNITE-6854 LLPL: https://github.com/pmem/pcj/tree/master/LLPL. Thanks, Mulugeta
Re: IEP-22: Direct Data Load proposal
Vladimir, Great IEP, but I couldn't comprehend the beginning of the "Direct Data Load" paragraph. Maybe, there are some typos? ср, 20 июн. 2018 г. в 18:08, Vladimir Ozerov : > Igniters, > > Initial data load is one of the most important use cases for our product. > This is one the first things user try to do with Ignite. And if it takes > too much time, it is very likely that user will look for other solutions. > Best regards, Andrey Kuznetsov.
Contribuition request: Random Forest
Hello, my name is Alexey Platonov. My Jira-id = aplatonov. I want to work on task IGNITE-8840. So please give me permissions for task assignment. Thanks. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
[jira] [Created] (IGNITE-8840) Random Forest
Yury Babak created IGNITE-8840: -- Summary: Random Forest Key: IGNITE-8840 URL: https://issues.apache.org/jira/browse/IGNITE-8840 Project: Ignite Issue Type: New Feature Components: ml Reporter: Yury Babak Fix For: 2.6 We want to implement random forest algorithm. It should be based on our implementation of decision trees. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: IEP-22: Direct Data Load proposal
Hello, Vladimir. Does this IEP fit with IEP-18: TDE? Do we allow to user to load data into encrypted cache? В Ср, 20/06/2018 в 18:08 +0300, Vladimir Ozerov пишет: > Igniters, > > Initial data load is one of the most important use cases for our product. > This is one the first things user try to do with Ignite. And if it takes > too much time, it is very likely that user will look for other solutions. > > We did good progress in this area recently. Specifically - a set of > internal improvements on our indexes, steaming mode for JDBC driver, COPY > command. But our internals are still not very efficient - every single > update goes through the whole set of Ignite components, such as page cache, > free-lists, BTrees, etc.. > > I created IEP-22 [1]. It's goal is to implement special direct data load > mode which will bypass our page cache and use alternative algorithm for > index updates. Together with COPY command and streaming this improvement > will allow Ignite to load data with very high speed. > > Please review the IEP and share your comments. > > Vladimir. > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-22%3A+Direct+Data+Load signature.asc Description: This is a digitally signed message part
IEP-22: Direct Data Load proposal
Igniters, Initial data load is one of the most important use cases for our product. This is one the first things user try to do with Ignite. And if it takes too much time, it is very likely that user will look for other solutions. We did good progress in this area recently. Specifically - a set of internal improvements on our indexes, steaming mode for JDBC driver, COPY command. But our internals are still not very efficient - every single update goes through the whole set of Ignite components, such as page cache, free-lists, BTrees, etc.. I created IEP-22 [1]. It's goal is to implement special direct data load mode which will bypass our page cache and use alternative algorithm for index updates. Together with COPY command and streaming this improvement will allow Ignite to load data with very high speed. Please review the IEP and share your comments. Vladimir. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-22%3A+Direct+Data+Load
[GitHub] ignite pull request #4232: IGNITE-8809: First steps.
GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/4232 IGNITE-8809: First steps. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8809 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4232.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 #4232 commit 49c00d16f09ec25dcd700e8fb6376ba3ce513c36 Author: Ivan Daschinskiy Date: 2018-06-20T14:35:18Z IGNITE-8809: First steps. ---
[GitHub] ignite pull request #4200: IGNITE-8749: Exception for "no space left" situat...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4200 ---
[GitHub] ignite pull request #4231: IGNITE-4380
GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/4231 IGNITE-4380 You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite IGNITE-4380 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4231.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 #4231 commit c80eb2fa3b2f12f514058eb759be6cc7b90106f2 Author: voipp Date: 2018-06-14T15:37:18Z #draft commit 0c7d5ee8cad09aaa446de8b12d7c5ed7c688 Author: voipp Date: 2018-06-18T09:29:54Z #loggings commit f77bb3feb23d46cf3af80631b9423e965929e79d Author: voipp Date: 2018-06-20T13:06:22Z #setting value into tx entry on primary prepare commit eeaa6f6ba9a60184e01752bb1774a2109bba939f Author: voipp Date: 2018-06-20T13:06:48Z Revert "#loggings" This reverts commit 0c7d5ee commit 96a41ffa8b1201607d986da1eccae02fdf69a2bb Author: voipp Date: 2018-06-20T13:07:31Z #fix commit 0f6e6366c3b61bc4341fccaa85c2e70c1cea649a Author: voipp Date: 2018-06-20T13:50:09Z #added writeVal flag. If this flag is enabled, than TxEntry.val will be marshalled and included into dht prepare message ---
[GitHub] ignite pull request #4230: IGNTIE-8792: Introduction of TensorFlow integrati...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4230 ---
[GitHub] ignite pull request #4230: IGNTIE-8792: Introduction of TensorFlow integrati...
GitHub user ybabak opened a pull request: https://github.com/apache/ignite/pull/4230 IGNTIE-8792: Introduction of TensorFlow integration module module added to root pom You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8792 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4230.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 #4230 commit 5bb52f1cbbcae9301b6d9cf092c03ca9ec350b89 Author: YuriBabak Date: 2018-06-15T12:07:21Z IGNITE-8792: TF integration module initial commit commit 2629b5f90733283bd8be58e481556f113cac6b5b Author: YuriBabak Date: 2018-06-15T16:39:58Z IGNITE-8792: TF integration module Readme fix commit c4296aedc7570ca195378ece8bce293e3df019ef Author: Yury Babak Date: 2018-06-15T16:40:26Z Merge branch 'apacheMaster' into ignite-8792 commit 15a360be3599c7d3032ac0dfdbfe49627adf202e Author: Yury Babak Date: 2018-06-20T12:24:32Z Merge branch 'apacheMaster' into ignite-8792 # Conflicts: # modules/tensorflow/pom.xml commit 760c3b7e744becbb618e60e9b7c049e9b9c24fc2 Author: YuriBabak Date: 2018-06-20T13:02:32Z IGNITE-8792: TF integration module module added into root pom ---
[GitHub] ignite pull request #4229: IGNITE-8797 cleanPersistenceDir() before stopAllG...
GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/4229 IGNITE-8797 cleanPersistenceDir() before stopAllGrids() You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite ignite-8797 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4229.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 #4229 commit d36cf94ba4bdf3f7f5bc27dce18a6a915fda55ac Author: Aleksey Plekhanov Date: 2018-06-20T12:35:08Z IGNITE-8797 cleanPersistenceDir() before stopAllGrids() ---
[jira] [Created] (IGNITE-8839) Throw meaningful and user-friendly exception when Ignite Persistence files are unaccessible
Ilya Lantukh created IGNITE-8839:
Summary: Throw meaningful and user-friendly exception when Ignite
Persistence files are unaccessible
Key: IGNITE-8839
URL: https://issues.apache.org/jira/browse/IGNITE-8839
Project: Ignite
Issue Type: Improvement
Reporter: Ilya Lantukh
Currently not having read+write permissions for persistence directory can lead
to exception like this:
{noformat}
2018-06-19 16:27:51 ERROR GridDhtPartitionsExchangeFuture:495 - Failed to
activate node components [nodeId=7ff3a67c-ed86-452a-9097-2626a0252a6e,
client=false, topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1]]
class org.apache.ignite.IgniteCheckedException: Error while creating file
page store
[file=/home/apache-ignite-fabric-2.4.0-bin/work/db/node02-119b5ab9-11ac-456b-8488-6ba8f6d51d69/cache-c091e548-b45a-49b4-b8ec-2cb5e27c7af6_ConversationMessages/part-95.bin]:
at
org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:98)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initDir(FilePageStoreManager.java:450)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initForCache(FilePageStoreManager.java:411)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initializeForCache(FilePageStoreManager.java:217)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:714)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClusterStateChangeRequest(GridDhtPartitionsExchangeFuture.java:844)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:596)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.nio.file.AccessDeniedException:
/home/bizruntime/ubiquitos/apache-ignite-fabric-2.4.0-bin/work/db/node02-119b5ab9-11ac-456b-8488-6ba8f6d51d69/cache-c091e548-b45a-49b4-b8ec-2cb5e27c7af6_ConversationMessages/part-95.bin
at
sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
at
sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at
sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at
sun.nio.fs.UnixFileSystemProvider.newFileChannel(UnixFileSystemProvider.java:177)
at java.nio.channels.FileChannel.open(FileChannel.java:287)
at java.nio.channels.FileChannel.open(FileChannel.java:335)
at
org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIO.(RandomAccessFileIO.java:43)
at
org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIOFactory.create(RandomAccessFileIOFactory.java:42)
at
org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIOFactory.create(RandomAccessFileIOFactory.java:37)
at
org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:78)
... 9 more
{noformat}
Or like this:
{noformat}
IgniteCheckedException: Error while creating file page store
[file=/home/apache-ignite-fabric-2.4.0-bin/work/db/node02-119b5ab9-11ac-456b-8488-6ba8f6d51d69/cache-c091e548-b45a-49b4-b8ec-2cb5e27c7af6_ConversationMessages/part-95.bin]:,
done=true, state=SRV, evtLatch=0,
remaining=[d62b8f0a-6ddc-4314-90f3-93ca24d44200], super=GridFutureAdapter
[ignoreInterrupts=false, state=DONE, res=java.lang.NullPointerException,
hash=812167532]]
class org.apache.ignite.IgniteCheckedException: null
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7244)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:207)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:159)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2347)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at
[GitHub] ignite pull request #4228: IGNITE-8838: Fixed issue with two inserts without...
GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/4228 IGNITE-8838: Fixed issue with two inserts without closing cursor. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8838 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4228.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 #4228 commit ea6da1e9df51eebcfac4eb6b8db4b65d22d31907 Author: Igor Sapego Date: 2018-06-20T11:04:15Z IGNITE-8838: Fixed issue with two inserts without closing cursor. ---
[jira] [Created] (IGNITE-8838) Query cursor is open after INSERT call
Pavel Vinokurov created IGNITE-8838: --- Summary: Query cursor is open after INSERT call Key: IGNITE-8838 URL: https://issues.apache.org/jira/browse/IGNITE-8838 Project: Ignite Issue Type: Bug Components: odbc, platforms, sql Affects Versions: 2.4 Reporter: Pavel Vinokurov Ignite ODBC driver returns open cursor for an insert command. AddStatusRecord: Adding new record: Query cursor is in open state already., rowNum: 0, columnNum: 0 SQLGetDiagField: SQLGetDiagField called: 1 PutString: value: HY010 SQLGetDiagField: SQLGetDiagField called: 2 SQLGetDiagRec: SQLGetDiagRec called SQLGetDiagRec: SQLGetDiagRec called SQLGetDiagRec: SQLGetDiagRec called SQLParamOptions: SQLParamOptions called SQLBindParameter: SQLBindParameter called: 1, 1, 12 SQLBindParameter: SQLBindParameter called: 2, 1, 12 SQLBindParameter: SQLBindParameter called: 3, 1, 12 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
