Ignite users and devs,
I'll be in NYC, Nov 21 presenting at NY-Scala meetup (
https://www.meetup.com/ny-scala/events/266240908/) on "Apache Ignite
- Insight and Creativity in Distributed Programming". 100% live coding
session with pretty cool tricks and pearls of modern distributed
programming
Ivan,
Thanks for the details. I've created a ticket to clarify the section of the
docs related to the collocated flag:
https://issues.apache.org/jira/browse/IGNITE-12382
-
Denis
On Mon, Nov 18, 2019 at 1:07 AM Ivan Pavlukhin wrote:
> Sergey, Denis,
>
> All aforementioned flags are needed to
Denis A. Magda created IGNITE-12382:
---
Summary: Clarify "collocated" flag documentation
Key: IGNITE-12382
URL: https://issues.apache.org/jira/browse/IGNITE-12382
Project: Ignite
Issue Type:
Alexey, thanks for the details and for reaching out this milestone with the
2.4 support.
Generally, I would advise us to merge the changes to the master only after
we confirm the failing tests are not regressions. We should either remove
them or replace them with some others or just fix.
-
Denis
Right, a few tests from 200 are failed due to known issue and couldnt be
fixed immediately, related to rare cases. These tests are copies of 2.3
tests and part of them could have no meaning for 2.4 due to Spark changed
behaviour.
пн, 18 нояб. 2019 г., 19:42 Denis Magda :
> Alexey,
>
> Please
Alexey,
Please help to understand what it means that 2.4 integration supports "95%
of tests of 2.3". Does it mean that 5% of existing tests are failing and,
basically, need to be fixed?
-
Denis
On Mon, Nov 18, 2019 at 6:52 AM Alexey Zinoviev
wrote:
> Dear Nikolay Izhikov, I've recreated the
Interesting bit. Thank you for sharing.
пн, 18 нояб. 2019 г. в 17:29, Dmitriy Pavlov :
>
> Sure, once one user clicks authorize server,
> 1) his/her credentials are stored in memory and
> 2) process of background checks of TC,builds,queue status is started. On
> top of that, triggering for new
Dear Nikolay Izhikov, I've recreated the PR for 2.4 initial support
The last commit
https://github.com/apache/ignite/pull/7058/commits/60386802299deedc6ed60bf4736e922201a67fb8
contains
real changes from Spark 2.3
I suggest to merge to master this initial solution with 95% support of
Spark 2.4
Sure, once one user clicks authorize server,
1) his/her credentials are stored in memory and
2) process of background checks of TC,builds,queue status is started. On
top of that, triggering for new builds is started.
TC Bot doesn't have standalone credentials for TC server(s) configured.
Only
Alexandr Shapkin created IGNITE-12381:
-
Summary: QueryParser: propagate H2 ErrorCode to IgniteSQLException
Key: IGNITE-12381
URL: https://issues.apache.org/jira/browse/IGNITE-12381
Project: Ignite
Dmitriy,
Could you please clarify TC Bot needs this "Authorization"? What
happens inside? Simply would like to understand.
пн, 18 нояб. 2019 г. в 14:57, Dmitriy Pavlov :
>
> Hi Ivan,
>
> If menu is hidden that means somebody already authorized the server. If one
> can see this menu item, this
Hi Ivan,
If menu is hidden that means somebody already authorized the server. If one
can see this menu item, this means none from users authorized it.
Authorization is required after restart. If service fails, there is shell
script that tries to establish it again. Probably TC Bot instance failed
PetrovMikhail created IGNITE-12380:
--
Summary: Add event for node validation failure.
Key: IGNITE-12380
URL: https://issues.apache.org/jira/browse/IGNITE-12380
Project: Ignite
Issue Type:
Hi Roman,
Thanks a lot for the answer (and the pull request). As I said initially, I was
under the impression that the reason was the lack of affinity.
I understand the reason and the current design and I think we all agreed that
this is not optimal and that it should be reworked in the new
Hi, Steve
This behavior is actually not a bug, but this is not obvious. I'll try
to explain.
When query parallelism = N is turned on, it means that each cache is
divided into N parts from the SQL point of view. Every SQL query is
executed independently over each particular part, and then
Ivan,
Thanks that is good news. I use ignite as a platform and not directly to exec
in-house application so these types of things are making the generic code less
generic .
Thanks a lot for the great work.
-Original Message-
From: Ivan Pavlukhin
Sent: Monday, November 18, 2019
Steve,
Yep, unfortunately query parallelism in current flavor is
counter-intuitive. But it was designed so =( As Roman wrote
> And of course this feature should also be available in the new engine, though
> it's architecture may be changed.
The architecture of parallel execution will be
Sergey, Denis,
All aforementioned flags are needed to tackle shortcomings in our SQL engine.
SqlFieldsQuery.collocated
Actually javadoc describes this flag quite well. Some bits from my
side. As all we know Ignite by default uses "collocated" query
execution model. Basically it means that joins
Dmitriy,
Would be glad to do it but cannot find "'Authorize Server' menu item
near the user
name". Where should it be (https://mtcga.gridgain.com/ or somewhere else)?
сб, 16 нояб. 2019 г. в 17:30, Dmitriy Pavlov :
>
> Hi Folks,
>
> Could someone from GG press the 'Authorize Server' menu item
19 matches
Mail list logo
