Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4629
---
Igniters,
I would like Mesos integration update be included in the upcoming release.Can
anyone review prs for the following issues?
IGNITE-9388: mesos IgniteProvider tries to access obsolete ignite.run or
download from slow archiveIGNITE-9408: Update mesos version
Roman Shtykh
On
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3871
---
Hi Ilya,
This is very useful. Is the compression going to be per-page, in which case
the dictionary is going to be kept inside of a page? Or do you have some
other design in mind?
D.
On Mon, Sep 3, 2018 at 10:36 AM, Ilya Kasnacheev
wrote:
> Hello again!
>
> I've been running various
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4675
IGNITE-9458: Changed behaviour of --mvcc flag in benchmark server.
Don't override ignite config's "mvccEnabled" property in benchmark server.
You can merge this pull request into a Git
Pavel Kuznetsov created IGNITE-9458:
---
Summary: SQL benchmarks: absence of "--mvcc" benchmark flag should
not overwrite config values
Key: IGNITE-9458
URL: https://issues.apache.org/jira/browse/IGNITE-9458
Hello again!
I've been running various compression parameters through cod dataset.
It looks like the best compression level in terms of speed is either 1 or 2.
The default for Zstd seems to be 3 which would almost always perform worse.
For best performance a dictionary of 1024 is optimal, for
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4647
---
Dmitriy,
The zookeeper timeouts were caused by my commit (I looked through the wrong
PR when was checking tests), already reverted from master.
As for the bot, does it already have the logic to detect continuous
timeouts and send notification only after a successful run? If not, I guess
we
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4674
IGNITE-9419 Async wait for caches registration and save during PME.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Hello!
Whoa, you certainly should not get a JVM crash in this case. Can you please
attach your XML config (as a file)? I will fill an issue if able to
reproduce.
Regards,
--
Ilya Kasnacheev
пн, 3 сент. 2018 г. в 18:19, wt :
> I am getting the following error when starting a single node
Hello!
Obviously, your Ignite depends on other Spring beans, which are NOT loaded
alongside grid configuration in this case.
Move them to another spring context, start it first, and then use
IgnitionEx#start(IgniteConfiguration, GridSpringResourceContext).
.. or have your own Ignite Spring bean
Igor Sapego created IGNITE-9457:
---
Summary: ODBC: Add connection attributes for streaming mode
Key: IGNITE-9457
URL: https://issues.apache.org/jira/browse/IGNITE-9457
Project: Ignite
Issue
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4673
Preliminary Binary Object compression with Zstd.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Igor Sapego created IGNITE-9456:
---
Summary: ODBC: Implement asynchronous writing for streaming
Key: IGNITE-9456
URL: https://issues.apache.org/jira/browse/IGNITE-9456
Project: Ignite
Issue
Pavel Pereslegin created IGNITE-9455:
Summary: Total allocated size memory metric is always zero for
metastore data region.
Key: IGNITE-9455
URL: https://issues.apache.org/jira/browse/IGNITE-9455
I'm new to Ignite and I would like to join Apache Ignite development.
My JIRA's login is ibessonov
Hi, Dmitriy,
I created a table with possible blockers [1] for the page with the latest
build analysis. Anton K. has reviewed it. Can you check and merge it?
Also, I created a button to notify PR about analisis results [2]. I used
GitHub statuses (example [3]), but to work it needs a token with
I am getting the following error when starting a single node cluster
(intellij) and then the instance crashes. I did have some persistence issues
so cleaned up the work dir after which this started happening
ignite-5885b9e6.log
thanks, found the anonymous class and created new ones with serializable
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
I have a project that starts fine if i start it like this
Ignite ig = Ignition.start("POC5-server.xml");
ig.cluster().active(true);
I need to however use the config file and also set other details before
starting so When i do this i get an error:
IgniteConfiguration cfg =
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4672
IGNITE-9428: Fix broken MvccQueryTrackerImpl.onDone() semantic.
Signed-off-by: Andrey V. Mashenkov
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/4671
Ignite 9448
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9448
Alternatively you can review and apply
Hello Maxim,
Welcome to the Ignite community! I've added you to the list of
contributors, you should now be able to assign tickets to yourself.
Get familiar with Apache Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process
Instructions
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4643
---
Hi. Igniters!
I create two PR [1,2] for two issues: IGNITE-9165 (close streams) [3] and
IGNITE-9160 (fix equals methods) [4]. Can you please review it? The changes
are quite small, tests are ok, flacky as usual.
[1] https://github.com/apache/ignite/pull/4481
[2]
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4351
---
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4670
IGNITE-9412: GDB convergence by error support
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9412
Alexey Kukushkin created IGNITE-9454:
Summary: SecurityPermissionSetBuilder fails to append system
permission CACHE_CREATE
Key: IGNITE-9454
URL: https://issues.apache.org/jira/browse/IGNITE-9454
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/4669
IGNITE-7855: Supported streaming mode in ODBC
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7855
Stepan Pilschikov created IGNITE-9453:
-
Summary: REST: UUID column type displayed like byte array
Key: IGNITE-9453
URL: https://issues.apache.org/jira/browse/IGNITE-9453
Project: Ignite
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/4668
Ignite 2.5.1 p13 zk test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-2.5.1-p13-zk-test
Alternatively
I'm new to Ignite and I would like to join Apache Ignite development.
My JIRA's login is Maxim.Pudov
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Ivan Daschinskiy created IGNITE-9452:
Summary: Correct GridInternalTaskUnusedWalSegmentsTest after
merging IGNITE-6552
Key: IGNITE-9452
URL: https://issues.apache.org/jira/browse/IGNITE-9452
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/4335
---
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4667
IGNITE-8823 Quick fix.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite ignite-8823-true
Alternatively you
Ivan Pavlukhin created IGNITE-9451:
--
Summary: Cache API update Cache.size according to SNAPSHOT
isolation
Key: IGNITE-9451
URL: https://issues.apache.org/jira/browse/IGNITE-9451
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4662
---
Petr,
Can you by any chance check if rackspace tests have actual keys? I've
created a ticket for the failing test [1].
[1] https://issues.apache.org/jira/browse/IGNITE-9444
пт, 31 авг. 2018 г. в 11:44, Alexey Goncharuk :
> The failure is not related to the change (verified in a separate branch
Ilya Borisov created IGNITE-9450:
Summary: Web console: remove manual rendering from ignite-icon
directive
Key: IGNITE-9450
URL: https://issues.apache.org/jira/browse/IGNITE-9450
Project: Ignite
Nikolay, Val, it would be good if we could reach agreement here so that I
can make the necessary modifications before the 2.7 cutoff.
Nikolay - would you be comfortable if I went ahead and made database=schema?
Stuart.
On Mon, Aug 27, 2018 at 10:22 PM Valentin Kulichenko <
Pavel Kovalenko created IGNITE-9449:
---
Summary: Lazy unmarshalling of discovery events in TcpDiscovery
Key: IGNITE-9449
URL: https://issues.apache.org/jira/browse/IGNITE-9449
Project: Ignite
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/4666
Ignite 1.8.20
Created for testing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.8.20
Alternatively you
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/4665
IGNITE-9426 IgniteAtomicSequence benchmarks
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9426
Hello, Nikolay!
Thank you for your interest in Python thin client.
The traceback suggests that you using Python 2.7. Unfortunately, my
client supports only Python versions 3.4 and later.
Since you are using the latest Ubuntu OS, chances are you already have a
recent Python 3 installed. Try
GitHub user gromtech opened a pull request:
https://github.com/apache/ignite/pull/4664
IGNITE-8987 Ignite hangs during getting of atomic structure afterâ¦
â¦autoactivation
You can merge this pull request into a Git repository by running:
$ git pull
Hello, Dmitry.
I tried to build your lib locally and it failed.
Error message and pip version are below.
Seems, we have to fix developer instructions.
Do we need specific version of pip or something?
I tried to use default versions.
I using Ubuntu Linux.
Hello, Igniters!
Please review my work on Ignite thin client library written in Python 3.
Pull request:
https://github.com/apache/ignite/pull/4278
Jira issue with initial proposal:
https://issues.apache.org/jira/browse/IGNITE-7782
The documentation is temporarily available at:
48 matches
Mail list logo
