Hi Developers,
Because of the sync issue, the following 3 commits were lost.
Please re-apply it to the master.
https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=b26bbb29d5fdd9d4de5187042778ebe3b8c6c42e
https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=6c562a997c0beb3a3cd9dd29
Thanks to Alexey Plehanov for noticing and Infra Team for fixing the issue:
https://issues.apache.org/jira/browse/INFRA-17950
пн, 4 мар. 2019 г. в 13:53, Dmitriy Pavlov :
> Hi Developers,
>
> Because of the sync issue, the following 3 commits were lost.
>
> Please re-apply it to the master.
>
> h
Thanks for keeping track of it, I've re-applied the following commits:
IGNITE-11199 Add extra logging for client-server connections in TCP
discovery - Fixes #6048. Andrey Kalinin* 04.03.2019 2:11
IGNITE-11322 [USABILITY] Extend Node FAILED message by add consistentId
if it exist - Fixes #6180.
Thanks, Ivan, these commits are in sync in GitHub & GitBox. Only one commit
remained, Vladimir O., please chime in
пн, 4 мар. 2019 г. в 14:03, Ivan Rakov :
> Thanks for keeping track of it, I've re-applied the following commits:
>
> IGNITE-11199 Add extra logging for client-server connections in
Hi Suraj,
I've added your account to the list of contributors, so now you can pick
and assign any issue you like. You can pick up unassigned issues, as well,
as assigned issues. For an assigned issue it is required to ask assignee if
he/she is going to continue to contribute or not.
You can find
Hi Denis,
Could you please chime in? I had not practiced website updates yet.
Sincerely,
Dmitriy Pavlov
сб, 2 мар. 2019 г. в 04:34, 李玉珏 <18624049...@163.com>:
> Hi,
>
> As for Ignite's chinese document, it was previously located on a cloud
> note-taking page with the address of:
>
> https://www
Ivan,
I like that Jetbrains inspections are integrated with IDE and TC out
of the box, but currently, they are working not well enough on TC.
Actually, they are not checking our source code at all.
Let's try a bit another approach and try to be IDE-agnostic with code
style checking. I've checked
Andrew Mashenkov created IGNITE-11466:
-
Summary: MVCC: Remove irrelevant tests from mvcc suites.
Key: IGNITE-11466
URL: https://issues.apache.org/jira/browse/IGNITE-11466
Project: Ignite
Hi Igniters!
I want to propose the new feature for Ignite - prewarming of page memory.
The essence of prewarming feature is that after restarting the node is to
load into memory those pages that were loaded before last shutdown. I have
implemented the PoC of prewarming of page memory, which m
Dmitriy Pavlov created IGNITE-11467:
---
Summary: Support Automatic modules for ignite-spring: Move of
classes to a separate package or jar
Key: IGNITE-11467
URL: https://issues.apache.org/jira/browse/IGNITE-11467
Igniters,
It seems that our pre-configured list of plugins a bit grow up.
The full list of them for now:
TestReconnectPlugin 1.0
StanByClusterTestProvider 1.0
PageMemory tracker plugin 1.0
TestDistibutedConfigurationPlugin 1.0
NodeValidationPluginProvider 1.0
I think we should move them to
Alexey Goncharuk created IGNITE-11468:
-
Summary: System caches should not survive client reconnect
Key: IGNITE-11468
URL: https://issues.apache.org/jira/browse/IGNITE-11468
Project: Ignite
Hi Igniters,
Because nobody is reacted here, I'm going to remove this dependency and all
dependent classes (if any) by lazy consensus after 72 h.
Sincerely,
Dmitriy Pavlov
пт, 1 мар. 2019 г. в 22:46, Dmitriy Pavlov :
> Full dependency tree you can find here
>
> https://github.com/apache/ignite/
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
Looks like everything is good now - all three commits were returned.
On Mon, Mar 4, 2019 at 2:04 PM Dmitriy Pavlov wrote:
> Thanks, Ivan, these commits are in sync in GitHub & GitBox. Only one commit
> remained, Vladimir O., please chime in
>
> пн, 4 мар. 2019 г. в 14:03, Ivan Rakov :
>
> > Than
Dmitriy Pavlov created IGNITE-11469:
---
Summary: Support Automatic modules for ignite-rest-http: resolve
package inference between Jetty & Tomcat
Key: IGNITE-11469
URL: https://issues.apache.org/jira/browse/IGNITE
Yury Gerzhedovich created IGNITE-11470:
--
Summary: Views don't show in Dbeaver
Key: IGNITE-11470
URL: https://issues.apache.org/jira/browse/IGNITE-11470
Project: Ignite
Issue Type: Task
Stanislav Lukyanov created IGNITE-11471:
---
Summary: JDBC: Thin driver should start with a random server to
connect
Key: IGNITE-11471
URL: https://issues.apache.org/jira/browse/IGNITE-11471
Projec
Dmitry,
Here are the sources, it's used to enable shared memory for communication
SPI: https://github.com/apache/ignite/tree/master/ipc/shmem
Don't remember all of the details why the binary is hosted in GridGain
repository but see nothing wrong here as long as the lib is licensed under
Apache 2.
Hi,
My bit here is that I build sources from ipc/shmem and launched Ignite
with freshly built library on Linux.
пн, 4 мар. 2019 г. в 21:51, Denis Magda :
>
> Dmitry,
>
> Here are the sources, it's used to enable shared memory for communication
> SPI: https://github.com/apache/ignite/tree/master/i
Denis, Ivan, thank you for replies.
Ok, if sources are there, can we rename this artifact to
org.apache.ignite.smem?
Sincerely,
Dmitriy Pavlov
пн, 4 мар. 2019 г. в 22:59, Павлухин Иван :
> Hi,
>
> My bit here is that I build sources from ipc/shmem and launched Ignite
> with freshly built librar
Thank you for clarifying everybody, this is valuable expertise.
On 2019/02/27 09:01:00, Ilya Kasnacheev wrote:
> Hello!>
>
> We also have this wonderful tool: https://mtcga.gridgain.com/>
>
> It keeps track of tests which are currently flaky or under investigation,>
> and given your change
Dmitriy and Dev,
Let's release Java 9 - 11 improvements that are already merged? In my
understanding, they address or soothe usability issues reported in the
original email.
I would take Ignite 2.7, merge the changes there and roll out 2.8 as soon
as we can.
-
Denis
On Tue, Feb 5, 2019 at 10:2
Previously we've discussed that 2.8 will be a separate release with
services redesign.
I feel it makes more sense to take master because is contain a number of
features, e.g. services, new hibernate version support, more stabilization
done.
So I suggest taking the master as our base branch for 2.
Hey folks,
While working with Ignite users, I keep seeing data models where a single
object (row) might contain many fields (100, 200, more...), and most of
them are strings.
Correct me if I'm wrong, but per my understanding, for every such field we
store an integer value to represent its length.
It can take more than a month to release from the master. Decent Java 11
support is crucial - the more we delay all the existing usability
improvements, the more users we are losing. Check my original email -
everyone stumbles upon those gaps.
-
Denis
On Mon, Mar 4, 2019 at 10:51 PM Dmitriy Pavl
I don't see too much difference in taking master as is (e.g. today) vs 2.7
branch. Originally proposed release probably can be named as 2.7.1.
Ignite compress also is in master, so for 2.8 it is natural to be master
based.
Moreover, please take a look at
https://issues.apache.org/jira/browse/IGNI
27 matches
Mail list logo
