Hello, Apache Ignite community.
Can you please enable contributor rights on IGNITE for my JIRA Username tyabuki.
Best regards
Toru Yabuki
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4599
---
Hi Nikolay,
Python [1], PHP [2], and Node.js [3] thin clients will get into the release.
Thanks,
p.
[1] https://jira.apache.org/jira/browse/IGNITE-7782
[2] https://jira.apache.org/jira/browse/IGNITE-7783
[3] https://jira.apache.org/jira/browse/IGNITE-
On Tue, Aug 21, 2018 at 12:20 PM,
Hi Ilya,
Sounds terrific! Is this part of the following Ignite enhancement proposal?
https://cwiki.apache.org/confluence/display/IGNITE/IEP-20%3A+Data+Compression+in+Ignite
--
Denis
On Thu, Aug 23, 2018 at 5:17 AM Ilya Kasnacheev
wrote:
> Hello!
>
> My plan was to add a compression section to
Added IGNITE-9365
On Thu, Aug 23, 2018 at 3:56 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Hi David,
>
> With the Docker image you can actually use additional libraries by
> providing URLs to JARs via EXTERNAL_LIBS property. Please refer to this
> page:
David Harvey created IGNITE-9365:
Summary: Force backups to different AWS availability zones using
only Spring XML
Key: IGNITE-9365
URL: https://issues.apache.org/jira/browse/IGNITE-9365
Project:
Is it a parameter of query? I see it in the list of OP_QUERY_SQL parameters,
but not in list of OP_QUERY_SCAN which I use
(https://apacheignite.readme.io/v2.6/docs/binary-client-protocol-sql-operations).
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hi David,
With the Docker image you can actually use additional libraries by
providing URLs to JARs via EXTERNAL_LIBS property. Please refer to this
page: https://apacheignite.readme.io/docs/docker-deployment
But anyway, I believe that such contribution might be very valuable for
Ignite. Feel
I need an affinityBackupFilter that will prevent backups from running in
the same AWS availability zone. (A single availability zone has the
characteristic that some or all of the EC2 instances in that zone can fail
together due to a single fault. You have no control over the hosts on
which the
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4609
---
Hi, do you have query timeout configured?
D.
On Thu, Aug 23, 2018 at 9:09 AM, dmitrievanthony
wrote:
> When I'm sending Scan Query request via Binary Client Protocol with very
> big
> page size I get OOM on the server node:
> java.lang.OutOfMemoryError: Java heap space at
>
Alexei Scherbakov created IGNITE-9364:
-
Summary: SetTxTimeoutOnPartitionMapExchangeTest.java hangs on TC
Key: IGNITE-9364
URL: https://issues.apache.org/jira/browse/IGNITE-9364
Project: Ignite
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4609
IGNITE-9363: Fix Jetty tests.
Minor refactoring.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9363
Andrew Mashenkov created IGNITE-9363:
Summary: Jetty tests forget to stop nodes on finished.
Key: IGNITE-9363
URL: https://issues.apache.org/jira/browse/IGNITE-9363
Project: Ignite
Issue
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4608
Remove SnapTreeMap. Remove IgniteInternalCache.isMongo*Cache().
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user antkr opened a pull request:
https://github.com/apache/ignite/pull/4607
Ignite 14071 2.4.9
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-14071-2.4.9
Alternatively you can review and
Vladimir Ozerov created IGNITE-9362:
---
Summary: SQL: Remove NODES.IS_LOCAL attribute
Key: IGNITE-9362
URL: https://issues.apache.org/jira/browse/IGNITE-9362
Project: Ignite
Issue Type: Task
Ilya Kasnacheev created IGNITE-9361:
---
Summary: Remove IgniteInternalCache.isMongo*Cache() and other such
stuff
Key: IGNITE-9361
URL: https://issues.apache.org/jira/browse/IGNITE-9361
Project:
When I'm sending Scan Query request via Binary Client Protocol with very big
page size I get OOM on the server node:
java.lang.OutOfMemoryError: Java heap space at
org.apache.ignite.internal.binary.streams.BinaryMemoryAllocatorChunk.reallocate(BinaryMemoryAllocatorChunk.java:69)
at
Ilya Kasnacheev created IGNITE-9360:
---
Summary: Destroy SnapTreeMap and related classes
Key: IGNITE-9360
URL: https://issues.apache.org/jira/browse/IGNITE-9360
Project: Ignite
Issue Type:
Github user AMashenkov closed the pull request at:
https://github.com/apache/ignite/pull/4546
---
Github user dwimsey closed the pull request at:
https://github.com/apache/ignite/pull/2812
---
Vyacheslav.
It looks like we able to restart all services on grid startup from old
definitions (inside cache) in case persistence turned on.
Se no problems to provide such automated migration case.
Also, we can test it using compatibility framework.
BTW, Is proposed solution provides the
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4606
Ignite 2.4.8 p2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.8-p2
Alternatively you can review and apply
Alex Volkov created IGNITE-9359:
---
Summary: OptimizeMakeChangeGAExample hangs forever with additional
nods in topology
Key: IGNITE-9359
URL: https://issues.apache.org/jira/browse/IGNITE-9359
Project:
I checked and it looks like the result is the same (or even worse, I get
1150ms with page size 1000, but the reason might be in other changes,
previous measures I did using 2.6).
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4602
---
Hello!
Can you check if there's any difference with
https://github.com/apache/ignite/pull/4592 ?
Regards,
--
Ilya Kasnacheev
2018-08-23 16:05 GMT+03:00 dmitrievanthony :
> Hi,
>
> I have a cache with 5000 objects, 400Kb each and I need to download all
> these objects using Binary Client
Hi,
I have a cache with 5000 objects, 400Kb each and I need to download all
these objects using Binary Client Protocol. To do than I use Scan Query (and
Load Next Page to load page 2, 3, etc...) request without any filter.
I measure the time between two moments: when request has been sent and
Hello, Vyacheslav.
Thanks, for sharing your design.
> I have a question about services migration from AI 2.6 to a new solution
Can you describe consequences of not having migration solution?
What will happen on the user side?
В Чт, 23/08/2018 в 14:44 +0300, Vyacheslav Daradur пишет:
> Hi,
Hello!
My plan was to add a compression section to cache configuration, where you
can enable compression, enable key compression (which has heavier
performance implications), adjust dictionary gathering settings, and in the
future possibly choose betwen algorithms. In fact I'm not sure, since my
Ok, thanks. IMO we need to store the dictionary in Durable memory before
merging into master.
чт, 23 авг. 2018 г. в 15:12, Ilya Kasnacheev :
> Hello!
>
> Currently, the dictionary for decompression is only stored on heap. After
> restart there's compressed data in the PDS, but there's no
Hello Steve,
I've looked at Persistent Collectors library, but don't see any big
advantages to use it inside Ignite right now.
Why do you think, that marshalling/unmarshalling process will be speeded up
with this library? As I can see there are no explicit changes in
serialization process, just
Hi Ilya
Is there a plan to introduce it as an option of Ignite configuration? In
that instead the boolean type I suggest to use the enum and reserve the
ability to extend compressions algorithms in future
On Thu, Aug 23, 2018 at 1:09 PM, Ilya Kasnacheev
wrote:
> Hello!
>
> I want to share with
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4605
IGNITE-8911
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8911-1
Alternatively you can review and apply
Github user EdShangGG closed the pull request at:
https://github.com/apache/ignite/pull/4291
---
Hi Ilya,
Thank you for sharing this here. I believe this contribution will be
accepted by the Community. Moreover, it shows so remarkable performance
boost.
I'm pretty sure this patch will be reviewed by Ignite Native Persistence
experts soon.
What do you mean by can't survive PDS node restart?
Ilya Kasnacheev created IGNITE-9358:
---
Summary:
DynamicIndexAbstractConcurrentSelfTest#testConcurrentRebalance is flaky
Key: IGNITE-9358
URL: https://issues.apache.org/jira/browse/IGNITE-9358
Hi, Igniters!
I’m working on Service Grid redesign tasks and design seems to be finished.
The main goal of Service Grid redesign is to provide missed guarantees:
- Synchronous services deployment/undeployment;
- Failover on coordinator change;
- Propagation of deployments errors across the
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4601
---
Hello!
I want to share with the developer community my compression prototype.
Long story short, it compresses BinaryObject's byte[] as they are written
to Durable Memory page, operating on a pre-built dictionary. Typical
compression ratio is 0.4 (meaning 2.5x compression) using custom
GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/4604
IGNITE-8971: make GridRestProcessor propagate error message
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user kukushal opened a pull request:
https://github.com/apache/ignite/pull/4603
IGNITE-9357 Spark Structured Streaming with Ignite as data source and sink
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/4602
Ignite 9340
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/ignite ignite-9340
Alternatively you can review and apply these changes
Would someone please review a PR for IGNITE-9290 [1] ?
I've add some fixes to PR #4556 [2] and TC looks fine [3].
Now,
* Explicit lock unlocking moved to background system pool thread.
* Exchange future doesn't care for unlocking at all.
* MvccManager discovery listener is responsible for
Alexey Kukushkin created IGNITE-9357:
Summary: Spark Structured Streaming with Ignite as data source and
sink
Key: IGNITE-9357
URL: https://issues.apache.org/jira/browse/IGNITE-9357
Project:
GitHub user dmitrievanthony opened a pull request:
https://github.com/apache/ignite/pull/4601
IGNITE-9338 Add connection data int env variables of TensorFlow worker
processes
You can merge this pull request into a Git repository by running:
$ git pull
Vladimir Ozerov created IGNITE-9355:
---
Summary: Document 3 new system views (nodes, node attributes,
baseline nodes)
Key: IGNITE-9355
URL: https://issues.apache.org/jira/browse/IGNITE-9355
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4575
---
GitHub user ygerzhedovich opened a pull request:
https://github.com/apache/ignite/pull/4600
Ignite 9274
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9274
Alternatively you can review and apply
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4498
---
The test is to be fixed later in
https://issues.apache.org/jira/browse/IGNITE-9082. Already muted. Please
ignore.
чт, 23 авг. 2018 г. в 2:37, :
> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
> *Recently
This new test if failed intentionally (to be fixed in a separate ticket),
muted on TC.
чт, 23 авг. 2018 г. в 2:37, :
> 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
>
Hi Igniters,
This test seems to be flaky. I hope I will update bot today with improved
unstable test detection.
The Bot will require 4 times to fail before notification, and 100 previous
runs will be analyzed instead of 50.
Sincerely,
Dmitriy Pavlov
чт, 23 авг. 2018 г. в 8:37, :
> Hi Ignite
Alex Volkov created IGNITE-9354:
---
Summary: HelloWorldGAExample hangs forever with additional nods in
topology
Key: IGNITE-9354
URL: https://issues.apache.org/jira/browse/IGNITE-9354
Project: Ignite
That's great but would you mind explaining to me how we can get rid of the
marshalling/unmarshalling? Because that would significantly speed up the
processes that run on the grid.
On Wed, Aug 22, 2018 at 3:36 AM Denis Magda wrote:
> Hello Steve,
>
> Intel folks are already contributing Intel
56 matches
Mail list logo
