Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New test failure in master
IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_10_500_8_16
Hello, Alexey.
Thanks for your feedback and clarification.
> you have to explicitly specify fields having the same name inside the Key and
> Value.
By all of this we just make Ignite more complex in favor of single, wrong
use-case.
Moreover, you hurt another use-cases with this feature.
I
Ivan Bessonov created IGNITE-13058:
--
Summary: GridCommandHandlerTest.testKillHangingRemoteTransactions
failed
Key: IGNITE-13058
URL: https://issues.apache.org/jira/browse/IGNITE-13058
Project:
Alexander Lapin created IGNITE-13060:
Summary: Tracing: initial implementation
Key: IGNITE-13060
URL: https://issues.apache.org/jira/browse/IGNITE-13060
Project: Ignite
Issue Type:
> «Why SQL sets both fields? I just want to set the key object field!»
The solution from IGNITE-12807 has backward compatible API: you have to
explicitly specify fields having same name inside the Key and Value.
Otherwise the semantics is as is.
Denis's solution (that I like) is a new API not
Manuel created IGNITE-13059:
---
Summary: When I activate write-behind with RDBMS Ignite isn't
starting
Key: IGNITE-13059
URL: https://issues.apache.org/jira/browse/IGNITE-13059
Project: Ignite
> Personally, I treat this as an anti-pattern that should have been influenced
> by some of the old Ignite examples.
+1
I don’t see any reason to support fields with the same name both in key and in
value from SQL.
Moreover, I think if we implement this feature then for some part of the users
Hi Maxim,
I recently had similar troubles related to ExecutorService and
exception handling. It was an unexpected behavior for me that
exceptions of any kind* thrown from Runnable in a following code:
executor.submit(() -> throw new RuntimeException())
were silently ignored.
I seemed to me
Nikolay,
I think you and I agree here: there is no problem at all if the user uses
K/Vs in domain model OR developed a domain-to-K/V mapper OR does not use SQL
DML.
I think we just have different experience as to how "popular" is the user's
unwillingness to use one of the three existing
Semyon Danilov created IGNITE-13061:
---
Summary: Grid could start with one wal segment
Key: IGNITE-13061
URL: https://issues.apache.org/jira/browse/IGNITE-13061
Project: Ignite
Issue Type:
Ivan Bessonov created IGNITE-13062:
--
Summary:
DistributedMetaStoragePersistentTest.testJoinNodeWithLongerHistory failed
Key: IGNITE-13062
URL: https://issues.apache.org/jira/browse/IGNITE-13062
Folks,
Just keeping you informed: I and my colleagues are highly interested in TDE
in general and keys rotations specifically, but we don't have enough time
so far.
We'll dive into this feature and participate in reviews next month.
--
Best Regards,
Ivan Rakov
On Sun, May 17, 2020 at 10:51 PM
Maxim Muzafarov created IGNITE-13063:
Summary: Bottom-up index rebuild
Key: IGNITE-13063
URL: https://issues.apache.org/jira/browse/IGNITE-13063
Project: Ignite
Issue Type: Improvement
+1 (binding)
Checked .NET packages and examples.
On Fri, May 22, 2020 at 2:38 PM Alexey Zinoviev
wrote:
> +1
>
> пт, 22 мая 2020 г. в 13:57, Nikolay Izhikov :
>
> > Dear Community,
> >
> > I have uploaded release candidate to
> > https://dist.apache.org/repos/dist/dev/ignite/2.8.1-rc1/
> >
+1
пт, 22 мая 2020 г. в 13:57, Nikolay Izhikov :
> Dear Community,
>
> I have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.8.1-rc1/
> https://dist.apache.org/repos/dist/dev/ignite/packages_2.8.1-rc1/
>
> The following staging can be used for testing:
>
Denis,
From technical point of view #3 doesn’t look so complex, but I’m not sure we
should consider a case when Ignite is a part of Oracle database because we are
a database.
But making Ignite a multilingual tool sounds like an interesting opportunity.
Regards,
Igor
> 22 мая 2020 г., в
Dear Community,
I have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.8.1-rc1/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.8.1-rc1/
The following staging can be used for testing:
https://repository.apache.org/content/repositories/orgapacheignite-1481
Ivan, does global timeout change through jmx in scope of this ticket ? If so,
can you add it ? Opposite we need additional ticket, i hope ? We still have no
somehow store for jmx changed params, every one need to remember that cluster
restart will reset this setting to default, in this case
david created IGNITE-13065:
--
Summary: Ignite Web Console 2.7.0 not working when scanning cache
Error: Cannot read property 'length' of null
Key: IGNITE-13065
URL: https://issues.apache.org/jira/browse/IGNITE-13065
Denis, I like your proposal and will be glad to participate in developing a
solution in that way.
In additional to Nikolay's opinion about your ideas I think it is important
to get Dmitry Frolov's (who started the discussion) and Alexey Sasov's (who
also voted for the having this enhancement)
https://issues.apache.org/jira/browse/IGNITE-13064 is raised with label
"newbie".
On Tue, May 19, 2020 at 4:10 PM Ivan Rakov wrote:
> Support this idea in general but why 5 minutes and not less?
>
> This value looks to me greater than any value that can possibly affect
> existing deployments
Alexey,
If you support my idea, why don't we go ahead and support it for upcoming
Ignite releases? We'll preserve existing key-value APIs for now and will
rather expand them with a new set of methods that no longer require to pass
a key object. We'll be glad to work together with you on an IEP.
Ivan Rakov created IGNITE-13064:
---
Summary: Set default transaction timeout to 5 minutes
Key: IGNITE-13064
URL: https://issues.apache.org/jira/browse/IGNITE-13064
Project: Ignite
Issue Type:
Hi everybody!
Currently Ignite doesn't have an ability to detect SQL performance
regressions between different versions. We have a Yardstick benchmark
module, but it has several drawbacks:
- it doesn't compare different Ignite versions
- it doesn't check the query result
- it doesn't have an
Ilya,
Mono 6.x is broken [1]. The fix is merged, but only included in nightly
builds [2].
Mono 5.x works.
Ignite.NET does not have official Mono support.
Please use .NET Core 2+ to test Ignite.NET (on any OS) [3].
[1] https://github.com/mono/mono/issues/18418
[2]
Hello!
+1 (binding)
Checked that .deb package installs and runs.
Checked node start and C++ build in -bin.
Checked source compilation and mono compilation in -src (note that running
with Mono is still broken, but problem is not new and seems to be on Mono
side).
Regards,
--
Ilya Kasnacheev
Hi Roman,
+1 for sure. On a side note, should we create a separate ASF/Git repository
for the project? Not sure we need to put the suite in the main Ignite repo.
-
Denis
On Fri, May 22, 2020 at 8:54 AM Roman Kondakov
wrote:
> Hi everybody!
>
> Currently Ignite doesn't have an ability to
+ 1 (binding)
Downloaded a binary version, started a cluster and ran some samples.
-
Denis
On Fri, May 22, 2020 at 3:57 AM Nikolay Izhikov wrote:
> Dear Community,
>
> I have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.8.1-rc1/
>
Great idea I think.
Can we also use the tool to compare, let's say, H2 indexing against Calcite
based one to detect possible issues when the new engine acts worse than H2?
Regards
Igor
пт, 22 мая 2020 г., 22:36 Denis Magda :
> Hi Roman,
>
> +1 for sure. On a side note, should we create a
Igniters,
Some of you knows I'm working on a new Apache Calcite based SQL query
execution engine now[1] and I succeeded a little in this [2].
This activity becomes more important after H2 community decided to remove a
set of interfaces that we are using in our integration[3].
In scope of my
30 matches
Mail list logo
