Distributed TensorFlow, awesome!
On Tue, Sep 25, 2018 at 12:53 PM Юрий Бабак wrote:
> Hello, Igniters.
>
> For release 2.7 we will introduce integration between TensorFlow and Apache
> Ignite. This integration contains changes on Apache Ignite side and on
> TensorFlow side.
>
> Apache Ignite par
Great addition, Yuriy!
Adding the "ignite-tensorflow" module makes total sense to me.
--
Denis
On Tue, Sep 25, 2018 at 12:53 PM Юрий Бабак wrote:
> Hello, Igniters.
>
> For release 2.7 we will introduce integration between TensorFlow and Apache
> Ignite. This integration contains changes on Ap
Hello, Igniters.
For release 2.7 we will introduce integration between TensorFlow and Apache
Ignite. This integration contains changes on Apache Ignite side and on
TensorFlow side.
Apache Ignite part is the command line tool which allows create and
maintain TensorFlow clusters over Apache Ignite
Hi,
I've made some investigation a couple of months ago about a statistics
collected by some RDBMS vendors (Oracle, Postgres, MySQL). These databases
collect detailed IO statistics in dimensions such as queries, database
objects (tables and indexes), files, sessions, users, event types etc.
Some
Andrey Kuznetsov created IGNITE-9695:
Summary: Add a way to prevent per-cache WAL disabling in
WalStateManager
Key: IGNITE-9695
URL: https://issues.apache.org/jira/browse/IGNITE-9695
Project: Igni
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4832
IGNITE-9540: MVCC TX: make cache invoke\invokeAll operations support Mvcc
tx mode.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/4831
IGNITE-9693 wip.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9693
Alternatively you can review and apply t
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4755
---
Hello Igniters.
As was discussed, IgniteSet implementation was based on on-heap data
duplication (setDataMap), as a result, the data was not recovered after
cluster restart and in the case of large data sets, this led to a
significant heap growing and gc pressure.
We changed the implementation so
asfgit closed pull request #18: IGNITE-9541 Hotfix for old cache
URL: https://github.com/apache/ignite-teamcity-bot/pull/18
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull
zzzadruga opened a new pull request #18: IGNITE-9541 Hotfix for old cache
URL: https://github.com/apache/ignite-teamcity-bot/pull/18
This is an automated message from the Apache Git Service.
To respond to the message, please
I like the idea.
On Tue, Sep 25, 2018 at 8:25 AM Dmitriy Pavlov
wrote:
> Hi Ignite Enthusiasts,
>
> During the planning of release 2.7, I've faced with the situation when it
> is completely not clear who is going to review ticket.
>
> Usually, we do not reassign tickets to a reviewer, but info a
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4830
IGNITE-9649 Debug logs enhacement
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9649
Alternatively you can revi
asfgit closed pull request #17: IGNITE-9541 Hotfix
URL: https://github.com/apache/ignite-teamcity-bot/pull/17
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4829
IGNITE-9686: JDK9: pass jdk9 specific JVM options to new process whenâ¦
⦠start Ignite test node in separate JVM
You can merge this pull request into a Git repository by running:
$
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/4828
IGNITE-9691 testConcurrentAuthorize uses outdated assumption about
exception message
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridga
Hi Ignite Enthusiasts,
During the planning of release 2.7, I've faced with the situation when it
is completely not clear who is going to review ticket.
Usually, we do not reassign tickets to a reviewer, but info about planned
reviewer can be very useful for all reviewers, who select some contribu
Ivan Bessonov created IGNITE-9694:
-
Summary: Do not block reading queries on exchange events that
don't change data visibility
Key: IGNITE-9694
URL: https://issues.apache.org/jira/browse/IGNITE-9694
P
zzzadruga opened a new pull request #17: IGNITE-9541 Hotfix
URL: https://github.com/apache/ignite-teamcity-bot/pull/17
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub
Github user asfgit closed the pull request at:
https://github.com/apache/ignite-release/pull/2
---
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite-release/pull/2
Fix gpg key regexp
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite-release vote-step-fix
Alternatively you can review an
Sergey Kosarev created IGNITE-9693:
--
Summary: Scale up wal compression workers to increase perormance
Key: IGNITE-9693
URL: https://issues.apache.org/jira/browse/IGNITE-9693
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4795
---
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/4827
IGNITE-9418 initialize cache persistent storage concurrently.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9418
Vyacheslav Daradur created IGNITE-9692:
--
Summary: Cache creation request may be missed on coordinator change
Key: IGNITE-9692
URL: https://issues.apache.org/jira/browse/IGNITE-9692
Project: Ignite
Oleg Ignatenko created IGNITE-9691:
--
Summary:
AuthenticationProcessorNodeRestartTest.testConcurrentAuthorize uses outdated
assumption about exception message
Key: IGNITE-9691
URL: https://issues.apache.org/jira/
Andrew Mashenkov created IGNITE-9690:
Summary: MVCC: Check mvcc operations behavior with LOST partitions.
Key: IGNITE-9690
URL: https://issues.apache.org/jira/browse/IGNITE-9690
Project: Ignite
Andrew Mashenkov created IGNITE-9689:
Summary: MVCC: Optimize filter usage in MvccUpdateDataRow.
Key: IGNITE-9689
URL: https://issues.apache.org/jira/browse/IGNITE-9689
Project: Ignite
Is
asfgit closed pull request #16: IGNITE-9668 Comment JIRA from pr.html
URL: https://github.com/apache/ignite-teamcity-bot/pull/16
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4826
IGNITE-8146: JDK9: fix gathering class loader's URLs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-814
Andrew Mashenkov created IGNITE-9688:
Summary: MVCC: Implement out-of-order enlist optimization for bulk
cache operations.
Key: IGNITE-9688
URL: https://issues.apache.org/jira/browse/IGNITE-9688
P
asfgit closed pull request #9: IGNITE-9541 Add the comparison for two general
statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displ
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4825
Ignite 8559 2.5
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8559-2.5
Alternatively you can review and apply
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4788
---
Taras Ledkov created IGNITE-9687:
Summary: JDK9: JTA tests failed
Key: IGNITE-9687
URL: https://issues.apache.org/jira/browse/IGNITE-9687
Project: Ignite
Issue Type: Task
Affects Versions
Taras Ledkov created IGNITE-9686:
Summary: JDK9: pass JVM options to new process when start remote
test node
Key: IGNITE-9686
URL: https://issues.apache.org/jira/browse/IGNITE-9686
Project: Ignite
Yury Babak created IGNITE-9685:
--
Summary: [ML] Add ignite-tensorflow module to build artifacts
Key: IGNITE-9685
URL: https://issues.apache.org/jira/browse/IGNITE-9685
Project: Ignite
Issue Type:
Taras Ledkov created IGNITE-9684:
Summary: JDK9: pass JVM options to created process at
HadoopCommandLineTest#createProcessBuilder
Key: IGNITE-9684
URL: https://issues.apache.org/jira/browse/IGNITE-9684
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4449
---
Pavel Kovalenko created IGNITE-9683:
---
Summary: Create manual pinger for ZK client
Key: IGNITE-9683
URL: https://issues.apache.org/jira/browse/IGNITE-9683
Project: Ignite
Issue Type: Improve
SomeFire opened a new pull request #16: IGNITE-9668 Comment JIRA from pr.html
URL: https://github.com/apache/ignite-teamcity-bot/pull/16
This is an automated message from the Apache Git Service.
To respond to the message, ple
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4769
---
JIRA ticket is some elementary change that needs to be reviewed. We don't
review the patch, we review ticket (with motivation, implementation
details, history of discussion), so reviewer will look at a ticket first.
PR does not have a mark, that it is ready to be merged. Some PRs are
created just
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/4824
IGNITE-9682 changed updatePartitionFullMap() method to update map in â¦
â¦parallel
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridga
GitHub user ygerzhedovich opened a pull request:
https://github.com/apache/ignite/pull/4823
Ignite-8580
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8580
Alternatively you can review and apply th
Oleg Ostanin created IGNITE-9682:
Summary: Update full partition map in parallel
Key: IGNITE-9682
URL: https://issues.apache.org/jira/browse/IGNITE-9682
Project: Ignite
Issue Type: Improvemen
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4822
IGNITE-9675: Deadlock on Ignite:active() and stopping grid simultaneously
calling
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/
Github user avplatonov closed the pull request at:
https://github.com/apache/ignite/pull/4806
---
Hello, Dmitriy
> What about the case when committer creates ignite-9679 branch and tests it>
> without PR?
It means, committer is experienced enough to run tests via Team City interface
:).
> So scanning seems to be possible only in JIRA
I don't understand you here.
You can retrieve comments
Hi Yuriy,
I think this is great idea. But we need to collect more details on how and
what to collect. I think one of the most interesting parts for us would be
index and data page usages, split by different "dimensions":
1) Global node statistics
2) Per-cache statistics
3) Per-index statistics
We
Nikolay Izhikov created IGNITE-9681:
---
Summary: Wrong GIT config in Team City release archive
Key: IGNITE-9681
URL: https://issues.apache.org/jira/browse/IGNITE-9681
Project: Ignite
Issue Ty
Thank you, I'll do it today.
2018-09-24 18:19 GMT+03:00 Dmitriy Pavlov :
> Awesome, thanks! Added you to list of contributors.
>
> Feel free to create a new page under https://cwiki.apache.
> org/confluence/display/IGNITE/Testing+and+benchmarking
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 24 сент. 2
52 matches
Mail list logo
