I believe that the meaning was:
> I propose to start with running queries VIEW first.
вт, 27 нояб. 2018 г. в 10:47, Vladimir Ozerov :
>
> I propose to start with running queries мшуц first. Once we have it, it
> will be easier to agree on final command syntax.
>
> On Fri, Nov 23, 2018 at 9:32 AM
Hi Srikanth,
Apache Ignite 2.6.0 should use H2 1.4.195. But you use H2 1.4.197. This is
the most likely cause of the error.
On Mon, Nov 26, 2018 at 5:47 PM srikanth.mer...@tcs.com <
srikanth.mer...@tcs.com> wrote:
> Hi
>
> Am trying to read data from Ignite cache from SPARK and facing below
I propose to start with running queries мшуц first. Once we have it, it
will be easier to agree on final command syntax.
On Fri, Nov 23, 2018 at 9:32 AM Павлухин Иван wrote:
> Hi,
>
> May be I am a little bit late with my thoughts about a command syntax.
> How do I see it is going to be used:
>
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5497
---
+1
Plus this dedicated list should be properly documented in wiki, mentioning
it in How to Contribute [1] or in Make Teamcity Green Again [2] would be a
good idea.
[1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
[2]
+1
вт, 27 нояб. 2018 г. в 09:22, Dmitrii Ryabov :
>
> 0
> вт, 27 нояб. 2018 г. в 02:33, Alexey Kuznetsov :
> >
> > +1
> > Do not forget notification from GitBox too!
> >
> > On Tue, Nov 27, 2018 at 2:20 AM Zhenya wrote:
> >
> > > +1, already make it by filers.
> > >
> > > > This was discussed
0
вт, 27 нояб. 2018 г. в 02:33, Alexey Kuznetsov :
>
> +1
> Do not forget notification from GitBox too!
>
> On Tue, Nov 27, 2018 at 2:20 AM Zhenya wrote:
>
> > +1, already make it by filers.
> >
> > > This was discussed already [1].
> > >
> > > So, I want to complete this discussion with moving
Evgenii Zhuravlev created IGNITE-10414:
--
Summary: IF NOT EXISTS in CREATE TABLE doesn't work
Key: IGNITE-10414
URL: https://issues.apache.org/jira/browse/IGNITE-10414
Project: Ignite
+1
Do not forget notification from GitBox too!
On Tue, Nov 27, 2018 at 2:20 AM Zhenya wrote:
> +1, already make it by filers.
>
> > This was discussed already [1].
> >
> > So, I want to complete this discussion with moving outside dev-list
> > GitHub-notification to dedicated list.
> >
> >
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5493
---
+1, already make it by filers.
This was discussed already [1].
So, I want to complete this discussion with moving outside dev-list
GitHub-notification to dedicated list.
Please start voting.
+1 - to accept this change.
0 - you don't care.
-1 - to decline this change.
This vote will go for
0 - don't care
--
Denis
On Mon, Nov 26, 2018 at 10:54 AM Eduard Shangareev <
eduard.shangar...@gmail.com> wrote:
> This was discussed already [1].
>
> So, I want to complete this discussion with moving outside dev-list
> GitHub-notification to dedicated list.
>
> Please start voting.
>
> +1 -
+1, definitely
On Mon, Nov 26, 2018 at 10:00 PM Ivan Rakov wrote:
> +1.
>
> I've already solved this issue for myself by creating an e-mail filter,
> but I see no reason why every new contributor should do the same.
>
> Best Regards,
> Ivan Rakov
>
> On 26.11.2018 21:56, Dmitriy Pavlov wrote:
>
+1.
I've already solved this issue for myself by creating an e-mail filter,
but I see no reason why every new contributor should do the same.
Best Regards,
Ivan Rakov
On 26.11.2018 21:56, Dmitriy Pavlov wrote:
+0.42 because 42 is an Answer to Life, the Universe, and Everything
пн, 26 нояб.
+0.42 because 42 is an Answer to Life, the Universe, and Everything
пн, 26 нояб. 2018 г. в 21:54, Eduard Shangareev :
> This was discussed already [1].
>
> So, I want to complete this discussion with moving outside dev-list
> GitHub-notification to dedicated list.
>
> Please start voting.
>
> +1
This was discussed already [1].
So, I want to complete this discussion with moving outside dev-list
GitHub-notification to dedicated list.
Please start voting.
+1 - to accept this change.
0 - you don't care.
-1 - to decline this change.
This vote will go for 72 hours.
[1]
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/5502
Ignite 10413
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10413
Alternatively you can review and apply these
Ok,
We need two approaches to change cache configuration:
1. Ignite.restartCaches(CacheConfiguration ... cfgs);
2. Ignite.restartCaches(CacheConfigurationDiff ... cfgDiffs);
Also, we need some versioning of cache configurations for caches. Which
could be done when we move the cache configuration
Ivan Rakov created IGNITE-10413:
---
Summary: Perform cache validation logic on primary node instead of
near node
Key: IGNITE-10413
URL: https://issues.apache.org/jira/browse/IGNITE-10413
Project: Ignite
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/5501
IGNITE-10412 Reproducer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-10412
Alternatively you can review and
Andrey Gura created IGNITE-10412:
Summary: Transaction tries prepare after commit
Key: IGNITE-10412
URL: https://issues.apache.org/jira/browse/IGNITE-10412
Project: Ignite
Issue Type:
Maxim,
I have looked through your algorithm of reading partition consistently.
And I have some questions/comments.
1. The algorithm requires heavy synchronization between checkpoint-thread
and new-approach-rebalance-threads,
because you need strong guarantees to not start writing or reading to
Pavel Tupitsyn created IGNITE-10411:
---
Summary: .NET: Allow conditional serialization override
Key: IGNITE-10411
URL: https://issues.apache.org/jira/browse/IGNITE-10411
Project: Ignite
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5500
IGNITE-10366: MVCC: Create "Cache 1" test suite for MVCC mode.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/5499
IGNITE-10049: Cache 4 test suite for MVCC mode.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10049
Roman Kondakov created IGNITE-10410:
---
Summary: MVCC: Create "Cache 7" test suite for MVCC mode.
Key: IGNITE-10410
URL: https://issues.apache.org/jira/browse/IGNITE-10410
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4927
---
It should be noticed that additional parameter TEST_SCALE_FACTOR was added.
This parameter with ScaleFactorUtil methods can be used for test size
scaling for different runs (like ordinary and nightly RunALLs). If someone
want to distinguish these builds he/she can apply scaling methods from
Hi
Am trying to read data from Ignite cache from SPARK and facing below error
while creating IgniteContext
val ic = new IgniteContext(sc, () =>new
IgniteConfiguration()).fromCache("PUBLIC")
Error:
java.lang.NoSuchFieldError: serializer
at
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5470
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5397
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5390
---
Igniters,
I prepared and IEP-24 [1] for so-called "partition pruning" optimization
for our SQL engine, which will allow us to determine target nodes
containing query data prior to query execution. We already use this
optimization for very simple scenarios - only one expression, no JOINs.
The
Sergey Chugunov created IGNITE-10409:
Summary: ExchangeFuture should be in charge on cancelling
rebalancing process
Key: IGNITE-10409
URL: https://issues.apache.org/jira/browse/IGNITE-10409
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5078
---
Roman Kondakov created IGNITE-10408:
---
Summary: Clean unused legacy code in tests marked with GG-11148
Key: IGNITE-10408
URL: https://issues.apache.org/jira/browse/IGNITE-10408
Project: Ignite
Aleksey Zinoviev created IGNITE-10407:
-
Summary: [ML] Add Multi-label multi-class classification trainer
and model
Key: IGNITE-10407
URL: https://issues.apache.org/jira/browse/IGNITE-10407
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5200
---
Vladimir,
I think it might work. So, if nobody minds I can start prototyping
edge-chasing approach.
пн, 26 нояб. 2018 г. в 14:32, Vladimir Ozerov :
>
> Ivan,
>
> The problem is that in our system a transaction may wait for N locks
> simultaneously. This may form complex graphs which spread
Ivan Daschinskiy created IGNITE-10406:
-
Summary: .NET Failed to run ScanQuery with custom filter after
server node restart
Key: IGNITE-10406
URL: https://issues.apache.org/jira/browse/IGNITE-10406
Aleksey Zinoviev created IGNITE-10405:
-
Summary: [ML] Refactor GaussianNaiveBayesTrainerExample to read
data sample from file
Key: IGNITE-10405
URL: https://issues.apache.org/jira/browse/IGNITE-10405
Ivan,
The problem is that in our system a transaction may wait for N locks
simultaneously. This may form complex graphs which spread between many
nodes. Now consider that I have a deadlock between 4 nodes: A -> B -> *C*
-> D -> A. I've sent a message from a and never reached D because C failed.
Hello!
I think we should un-ignore these tests. You can even create a sub-task
under https://issues.apache.org/jira/browse/IGNITE-9210
Regards,
--
Ilya Kasnacheev
пн, 26 нояб. 2018 г. в 14:20, Andrey Mashenkov :
> Hi Igniters,
>
>
> I've found "Cache 1" TC suite actually
> starts
Hi Igniters,
I've found "Cache 1" TC suite actually
starts IgniteBinaryCacheTestSuite.class suite.
This suite ignores several tests that has copies to be run with binary
marshaller:
* DataStreamProcessorSelfTest
* GridCacheAffinityRoutingSelfTest
* IgniteCacheAtomicLocalExpiryPolicyTest
*
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5481
---
I see, thanks!
> On 26 Nov 2018, at 11:46, Roman Kondakov wrote:
>
> Hi, Petr!
>
> Actually these tests do not behave exactly as one test, but they behave
> mostly as one test. Often this is expressed in the following: we have a
> feature to test (i.e. transaction isolation) and different
Hi, Petr!
Actually these tests do not behave exactly as one test, but they behave
mostly as one test. Often this is expressed in the following: we have a
feature to test (i.e. transaction isolation) and different sets of
parameters to be tested with this feature: cache mode, backups number,
Hi, Roman.
> On 25 Nov 2018, at 21:26, Roman Kondakov wrote:
>
> Hi Dmitriy!
>
> We have over 50 000 test in our tests base. And this number will be
> noticeably increased soon by MVCC tests coverage activity. This means that it
> is very difficult to rework and rewrite these test manually
Igor,
Could you please clarify some points?
> 1) preserve list of active txs, sorted by the time of their first update
> (using WAL ptr of first WAL record in tx)
Is this list maintained per transaction or per checkpoint (or per
something else)? Why can't we track only oldest active
49 matches
Mail list logo
