Sergey Chugunov created IGNITE-11459:
Summary: Possible dead code in TcpDiscoveryStatusCheckMessage flow
Key: IGNITE-11459
URL: https://issues.apache.org/jira/browse/IGNITE-11459
Project: Ignite
Jinil Lee created IGNITE-11458:
--
Summary: ClassCastException when reading objects in Collection and
Map from ClientCache
Key: IGNITE-11458
URL: https://issues.apache.org/jira/browse/IGNITE-11458
Would add opens require user to set up a longer line?
пт, 1 мар. 2019 г., 9:01 Павлухин Иван :
> By the way. It is interesting that Unsafe class is not the source of
> warnings. I checked (with java 10) that there is no warnings issued
> when Unsafe instance is accessed with good old reflective
By the way. It is interesting that Unsafe class is not the source of
warnings. I checked (with java 10) that there is no warnings issued
when Unsafe instance is accessed with good old reflective way.
пт, 1 мар. 2019 г. в 08:05, Павлухин Иван :
>
> Here is how our friends from Hazelcast tackle the
Alexey,
My congratulations! Ignite ML rocks!
чт, 28 февр. 2019 г. в 16:16, Dmitriy Pavlov :
>
> Dear Ignite Developers,
>
>
>
> The Project Management Committee (PMC) for Apache Ignite has invited Alexey
> Zinoviev to become a committer and we are pleased to announce that he has
> accepted.
>
>
Here is how our friends from Hazelcast tackle the problem [1]. Using
--add-opens as Stan proposed looks like a good option in short
perspective. By the way to determine all illegally accessed packages
we can use --illegal-access=warn, which does not deny operation but
only prints a warning. I
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
Flags/hacks is not a way to go for serious and mature projects like Ignite.
We should switch to another mode - how to replace Unsafe completely.
-
Denis
On Thu, Feb 28, 2019 at 4:32 AM Dmitriy Pavlov wrote:
> > may become unavailable in any time.
>
> I remember this was discussed in 2013 that
Dmitriy Sorokin created IGNITE-11457:
Summary: Prewarming of page memory after node restart
Key: IGNITE-11457
URL: https://issues.apache.org/jira/browse/IGNITE-11457
Project: Ignite
Yury Gerzhedovich created IGNITE-11456:
--
Summary: Use separate pool for KILL QUERY command
Key: IGNITE-11456
URL: https://issues.apache.org/jira/browse/IGNITE-11456
Project: Ignite
Pavel Kovalenko created IGNITE-11455:
Summary: Introduce free lists rebuild mechanism
Key: IGNITE-11455
URL: https://issues.apache.org/jira/browse/IGNITE-11455
Project: Ignite
Issue
Alexey Goncharuk created IGNITE-11454:
-
Summary: Race in ClientImpl may lead to client node segmentation
on fast reconnect
Key: IGNITE-11454
URL: https://issues.apache.org/jira/browse/IGNITE-11454
Hi Igniters,
please be careful with ticket creation, In case you creating a ticket by
mistake, resolve and close it as won't fix.
Now I see two https://issues.apache.org/jira/browse/IGNITE-11429 and
https://issues.apache.org/jira/browse/IGNITE-11430 - it is the same ticket.
Also if you expect
Hi Ivan,
Yes, you catch me, I'm a little bit cheating with lazy consensus on code
modification without providing a PR because I was expecting that nobody
comes to discussion. I will prepare PR shortly. And since we anyway have a
discussion, I will not apply anything by lazy approval.
-
Stan, I thnk we never know the truth here. Imagine you never dealed with
distributed systems. You just copy distibs to intended machines and startup
distributed cluster out of the box. Is not it good? If we do the change we
should expect many questions to user@ asking why nodes do not see each
Yakov,
I checked hazelcast - it uses multicast by default.
чт, 28 февр. 2019 г., 14:31 Stanislav Lukyanov :
> Yakov,
>
> Our product is for engineers sitting in one office.
> Companies which use Ignite have many engineers running Ignite on their
> laptops the same way
> as companies that make
Taras Ledkov created IGNITE-11453:
-
Summary: SQL: command to wotk with permission must thrown clear
exception witn UNSUPPORTED error code
Key: IGNITE-11453
URL: https://issues.apache.org/jira/browse/IGNITE-11453
Yury Gerzhedovich created IGNITE-11451:
--
Summary: SQL system view for IO indexes statisitcs
Key: IGNITE-11451
URL: https://issues.apache.org/jira/browse/IGNITE-11451
Project: Ignite
Yury Gerzhedovich created IGNITE-11452:
--
Summary: KILL QUERY for not cancellable queries should return error
Key: IGNITE-11452
URL: https://issues.apache.org/jira/browse/IGNITE-11452
Project:
Taras Ledkov created IGNITE-11450:
-
Summary: SQL: HELP and SHOW commands must throw clear exception
with UNSUPPORTED error code
Key: IGNITE-11450
URL: https://issues.apache.org/jira/browse/IGNITE-11450
Yury Babak created IGNITE-11449:
---
Summary: [ML] API for Feature/Label extracting
Key: IGNITE-11449
URL: https://issues.apache.org/jira/browse/IGNITE-11449
Project: Ignite
Issue Type:
Thank you, Dmitriy.
чт, 28 февр. 2019 г. в 15:43, Dmitriy Pavlov :
>
> Hi Pavel,
>
> Please check now, I've added permissions.
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 27 февр. 2019 г. в 11:26, Pavel Pereslegin :
>
> > Hi, Igniters!
> >
> > I'm starting work on IGNITE-7935 (add a batch update
Dear Ignite Developers,
The Project Management Committee (PMC) for Apache Ignite has invited Alexey
Zinoviev to become a committer and we are pleased to announce that he has
accepted.
Being a committer enables easier contribution to the project since there is
no need to go via the patch
Hi Pavel,
Please check now, I've added permissions.
Sincerely,
Dmitriy Pavlov
ср, 27 февр. 2019 г. в 11:26, Pavel Pereslegin :
> Hi, Igniters!
>
> I'm starting work on IGNITE-7935 (add a batch update operation to
> PageMemory and Persistence) [1], this task is big enough to create an
> IEP for
Ivan, thanks, great consideration.
And probably for this warning, Java will probably resist to redirecting it
at Java level.
Anyway, we could try it because we know where the first Unsafe call is
performed in Ignite.
чт, 28 февр. 2019 г. в 09:36, Павлухин Иван :
> Also it worth to consider a
> may become unavailable in any time.
I remember this was discussed in 2013 that Unsafe will be removed soon. But
nothing is changed yet, so I hope unsafe will be available for a long time
(with flags/hacks/etc).
чт, 28 февр. 2019 г. в 09:11, Petr Ivanov :
> According to warning message, there
Why not? If Apache Kafka uses TeamCity, JIRA and GitHub, then Apache Ignite
TeamCity Bot is reusable there. It may require to apply a number of patches
to make heuristics configurable, Ignite-specific logic disablable, etc, but
it is possible to reuse.
I would be happy if Bot will have a number
Hi Maxim,
I agree with Denis and I have just one concern here.
Apache Ignite has quite a long story (started even before Apache), and now
it has a way too huge number of features. Some of these features
- are developed and well known by community members,
- some of them were contributed a long
Yakov,
Our product is for engineers sitting in one office.
Companies which use Ignite have many engineers running Ignite on their laptops
the same way
as companies that make changes to Ignite.
“Could it be because of the multicast?” is one of the questions I ask every
time I see a question on
Roman Kondakov created IGNITE-11448:
---
Summary: SQL: Wrong results of select with aggregates in subquery
Key: IGNITE-11448
URL: https://issues.apache.org/jira/browse/IGNITE-11448
Project: Ignite
Yury Gerzhedovich created IGNITE-11445:
--
Summary: Usability improvements for TABLES system SQL view
Key: IGNITE-11445
URL: https://issues.apache.org/jira/browse/IGNITE-11445
Project: Ignite
Yury Gerzhedovich created IGNITE-11447:
--
Summary: Replacements for default values in System SQL views.
Key: IGNITE-11447
URL: https://issues.apache.org/jira/browse/IGNITE-11447
Project: Ignite
Yury Gerzhedovich created IGNITE-11446:
--
Summary: Common prefix for local node system SQL view
Key: IGNITE-11446
URL: https://issues.apache.org/jira/browse/IGNITE-11446
Project: Ignite
Taras Ledkov created IGNITE-11444:
-
Summary: SQL: MERGE USING throws unclear exception
Key: IGNITE-11444
URL: https://issues.apache.org/jira/browse/IGNITE-11444
Project: Ignite
Issue Type:
Guys,
I remember we did the opposite change some time ago - switched VM IP finder
to multicast. That was done for user being able to start cluster spanning
multiple machines using examples configuration. With this change you
removed all the working samples for starting really distributed
Yury Gerzhedovich created IGNITE-11443:
--
Summary: usability improvements for INDEXES system SQL view
Key: IGNITE-11443
URL: https://issues.apache.org/jira/browse/IGNITE-11443
Project: Ignite
Yury Gerzhedovich created IGNITE-11441:
--
Summary: ignite-sys-cache present in SQL schemas
Key: IGNITE-11441
URL: https://issues.apache.org/jira/browse/IGNITE-11441
Project: Ignite
Issue
Yury Gerzhedovich created IGNITE-11442:
--
Summary: Renaming IGNITE schema to something more clear SYS,
SYSTEM, ...
Key: IGNITE-11442
URL: https://issues.apache.org/jira/browse/IGNITE-11442
Guys, I remember we did this to
--Yakov
ср, 27 февр. 2019 г. в 14:46, Dmitrii Ryabov :
> Hello, Igniters!
>
> Code is ready and reviewed, tests are passed.
>
> Can we make final decision about this change? Do we really need it? [1]
>
> Pros:
>
> * Multicast ipFinder adds some instability when
Yury Gerzhedovich created IGNITE-11440:
--
Summary: H2 SHOW commands support
Key: IGNITE-11440
URL: https://issues.apache.org/jira/browse/IGNITE-11440
Project: Ignite
Issue Type: Task
Guys,
The issue is that we chose the easiest way to start working with Java 9+,
which is the illegal-access=permit.
This is a blanket option that affects the whole VM which is better to avoid –
hence the warnings.
A better solution is to use --add-opens statements.
Same as add-exports, one
Dmitry,
I seems to me that the algorithm of using different schemes
for persistence folder naming is flawe.
Why don’t we just name the folder same as consistent ID all the time?
How about the following algorithm of db folder and consistenID generation
1.. If the consistent ID is explicitly set
Roman Kondakov created IGNITE-11439:
---
Summary: MVCC: Error in transaction mode validation.
Key: IGNITE-11439
URL: https://issues.apache.org/jira/browse/IGNITE-11439
Project: Ignite
Issue
43 matches
Mail list logo
