Thank you so much Denis.
Regards,
Saikat
On Mon, Aug 27, 2018 at 5:00 PM, Denis Magda wrote:
> Hello Saikat,
>
> Thanks for the article and contribution. We'll get it added to:
> https://ignite.apache.org/blogs.html
>
> --
> Denis
>
> On Sun, Aug 26, 2018 at 2:59 PM Saikat Maitra
> wrote:
>
>
GitHub user tyabuki opened a pull request:
https://github.com/apache/ignite/pull/4629
IGNITE-9382 Fixed data handling for multiple chunks of data
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tyabuki/ignite ignite-9382
Hi Mikhail!
Done, welcome to the community!
--
Denis
On Mon, Aug 27, 2018 at 6:52 AM Mikhail Petrov
wrote:
> I'm new to Ignite and I would like to join Apache Ignite development.
> My JIRA's login: PetrovMikhail
>
Hello Saikat,
Thanks for the article and contribution. We'll get it added to:
https://ignite.apache.org/blogs.html
--
Denis
On Sun, Aug 26, 2018 at 2:59 PM Saikat Maitra
wrote:
> Hello,
>
> I recently published blog on how we can stream data using Apache Ignite and
> Flink. This uses
Agree with Val. I think all users would expect that a service is restarted
upon a node or cluster restart. Let's make sure we preserve this behavior.
D.
On Fri, Aug 24, 2018 at 4:17 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Guys,
>
> I believe we should preserve the
Hi Nikolay,
I think it's actually pretty unfortunate that Spark uses term "database"
here, as it essentially refers to a schema in my view. Usually, database is
something you create a physical connection to, and connection is bind to
that database. To connect to another database you need to
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/4628
IGNITE-9393: Fixed bug in reduce function in dataset.compute
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4627
IGNITE-7259: tests fixed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-7259
Alternatively you can
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/4626
IGNITE-9389 Avoid deadlocks on cache#close()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9389
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4483
---
SomeFire opened a new pull request #4: show critical failures on top of the
results page
URL: https://github.com/apache/ignite-teamcity-bot/pull/4
This is an automated message from the Apache Git Service.
To respond to the
Aleksey Zinoviev created IGNITE-9393:
Summary: [ML] KMeans fails on complex data in cache
Key: IGNITE-9393
URL: https://issues.apache.org/jira/browse/IGNITE-9393
Project: Ignite
Issue
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4625
IGNITE-9392 : Specified TX timeout in test configuration.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9392
Ilya Lantukh created IGNITE-9392:
Summary: CacheAsyncOperationsFailoverTxTest hangs on TC
Key: IGNITE-9392
URL: https://issues.apache.org/jira/browse/IGNITE-9392
Project: Ignite
Issue Type:
Correct, this also needs to be fixed.
On Mon, Aug 27, 2018 at 5:17 PM Evgenii Zhuravlev
wrote:
> Vladimir,
>
> Then it looks like we send wrong EVT_CACHE_QUERY_EXECUTED events too, since
> we send it for the same cache, as in your example.
>
> Evgenii
>
>
>
> пн, 27 авг. 2018 г. в 13:20,
Vladimir,
Then it looks like we send wrong EVT_CACHE_QUERY_EXECUTED events too, since
we send it for the same cache, as in your example.
Evgenii
пн, 27 авг. 2018 г. в 13:20, Vladimir Ozerov :
> Folks,
>
> Can we leave query details metrics API unchanged, and simply fix how we
> record them?
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4624
IGNITE-9391 added checking result on waitForCondition in testRebalancâ¦
â¦eEstimateFinishTime
You can merge this pull request into a Git repository by running:
$ git pull
Anton Kalashnikov created IGNITE-9391:
-
Summary: Incorrect calculated esitmated rabalancing finish time
Key: IGNITE-9391
URL: https://issues.apache.org/jira/browse/IGNITE-9391
Project: Ignite
zzzadruga opened a new pull request #3: IGNITE-9333 Add statistics page
URL: https://github.com/apache/ignite-teamcity-bot/pull/3
This is a draft version
This is an automated message from the Apache Git Service.
To respond to
I'm new to Ignite and I would like to join Apache Ignite development.
My JIRA's login: PetrovMikhail
Andrew Mashenkov created IGNITE-9390:
Summary: MVCC: add MVCC support to .NET configuration.
Key: IGNITE-9390
URL: https://issues.apache.org/jira/browse/IGNITE-9390
Project: Ignite
Issue
Denis Mekhanikov created IGNITE-9389:
Summary: Concurrent Cache#close and put/get operations lead to a
deadlock
Key: IGNITE-9389
URL: https://issues.apache.org/jira/browse/IGNITE-9389
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4552
---
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4623
IGNITE-9373: Fix mvcc tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNITE-9373
Alternatively you can
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4572
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4574
---
According to my benchmarks - zstd compression algorithm [1] looks very
interesting, it has a high compression ratio with quite good speed.
AFAIK it supports external dictionaries, but I'm not sure about using
it with "on the fly building" dictionaries. Anyway, have look at (it
has ASF 2.0 friendly
Roman Shtykh created IGNITE-9388:
Summary: IgniteProvider tries to access obolete ignite.run or
download from slow archive
Key: IGNITE-9388
URL: https://issues.apache.org/jira/browse/IGNITE-9388
Hello Vyacheslav!
Unfortunately I have not found any efficient algorithms that will allow me
to use external dictionary as a pre-processed data structure. If plain gzip
is used without dictionary, the compression is around 0.7, as opposed to
0.4 that I will get with custom implementation, AFAIR
Yury Babak created IGNITE-9387:
--
Summary: [ML] Model updating
Key: IGNITE-9387
URL: https://issues.apache.org/jira/browse/IGNITE-9387
Project: Ignite
Issue Type: Improvement
Alexei Scherbakov created IGNITE-9386:
-
Summary: control.sh --tx can produce confusing results when limit
is set to small value
Key: IGNITE-9386
URL: https://issues.apache.org/jira/browse/IGNITE-9386
I believe, you should file a ticket on this one.
Best Regards,
Igor
On Fri, Aug 24, 2018 at 5:57 PM dmitrievanthony
wrote:
> I've rebuilt Ignite from master and tried again, but the behaviour is the
> same. If the page is very big (compare with heap size) server node fails
> with OOM and the
Dmitriy Shabalin created IGNITE-9385:
Summary: Redesign and Refactor UI part 2
Key: IGNITE-9385
URL: https://issues.apache.org/jira/browse/IGNITE-9385
Project: Ignite
Issue Type:
GitHub user gromtech opened a pull request:
https://github.com/apache/ignite/pull/4621
IGNITE-9367 CPP: ODBC client crashes after executing queryâ¦
...by using a closed connection
You can merge this pull request into a Git repository by running:
$ git pull
Folks,
Can we leave query details metrics API unchanged, and simply fix how we
record them? Historically it worked as follows:
1) IgniteCache.query() is invoked
2) Query is executed, possibly on other caches!
3) Metric is incremented for cache from p.1
I.e. our query detail metrics were broken
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4620
IGNITE-9265: MVCC TX: Two rows with the same key in one MERGE statement
produce an exception
Tests added.
You can merge this pull request into a Git repository by running:
$ git pull
Folks, this is a new failure in IGFS/Hadoop domain. Looks like the
http://www.us.apache.org/dist/hadoop/core/hadoop-2.5.2/hadoop-2.5.2.tar.gz
was moved (the URL gives 404).
Vladimir, can you take a look or point community how to take care of this
failure? Should we simply upgrade the Hadoop
This can be ignored for now, last 10 runs are green.
сб, 25 авг. 2018 г. в 15:12, :
> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
> *New test failure in master IgniteCoreTest: CacheTestSuite:
> TestPutGetTime
>
Alexey Goncharuk created IGNITE-9384:
Summary: Transaction state PREPARED may be set too early or too
late
Key: IGNITE-9384
URL: https://issues.apache.org/jira/browse/IGNITE-9384
Project: Ignite
Evgenii Zhuravlev created IGNITE-9383:
-
Summary: Add to the documentation that Ignite cluster requires
that each nodes have direct connection to any nodes of grid.
Key: IGNITE-9383
URL:
Hi Igniters!
Ilya, I'm glad to see one more person who is interested in the
compression feature in Ignite.
I looked through the pull request and want to share following thoughts:
It's very dangerous using a custom algorithm in this way - you store
serialized data separate from a dictionary and
Dmitry,
Not sure I understand the issue, but I see no reason to rollback anything.
In case we have some issues, let's just fix them.
сб, 25 авг. 2018 г. в 0:53, Dmitriy Pavlov :
> Hi Anton,
>
> Do you have objections about a partial rollback of changes?
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 24
Roman Shtykh created IGNITE-9382:
Summary: Node.js fails to process large payloads
Key: IGNITE-9382
URL: https://issues.apache.org/jira/browse/IGNITE-9382
Project: Ignite
Issue Type: Bug
Hi,
I have updated the PR with additional tests.
Please review and share feedback.
This PR is related to IgniteSink but allows to stream data from Ignite.
PR https://github.com/apache/ignite/pull/870/files
Review https://reviews.ignite.apache.org/ignite/review/IGNT-CR-135
Regards,
Saikat
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*Recently contributed test failed in master
org.apache.ignite.testsuites.IgniteIgfsLinuxAndMacOSTestSuite.initializationError
45 matches
Mail list logo
