Sergey,
I understand and support the proposed idea. Just curious how to
implement it. Do you already have some prototype?
пт, 31 янв. 2020 г. в 11:48, schernolyas :
>
> Hi!
>
> It is proposed to use the same annotation(RepositoryConfig). But value of
> field "cacheName" can be constant or Spring
> I think this case should fail with error like "only cache created tables
> can be removed with drop table. ", not with "scheme not found."
> SQL-engine is supposed to accept and understand values it returns itself.
Agree. Feel free to contribute a fix. My expectation here is that it
will not be
I merged PR and resolved the issue [1].
[1] https://issues.apache.org/jira/browse/IGNITE-12554
вт, 28 янв. 2020 г. в 08:45, Ivan Pavlukhin :
>
> Igniters,
>
> I prepared PR removing custom ThreadGroup for a ticket [1]. Everybody
> is welcome to review. If there will be no objections I am going to
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
Alex Scherbakof, as the one who created the ticket, could you please help
Artem and share more details?
-
Denis
On Fri, Jan 31, 2020 at 4:54 AM Artem Demchenko
wrote:
> Hi, everyone! I have a question about the following task:
> https://issues.apache.org/jira/browse/IGNITE-11663.
>
> The descr
Back up Ivan's opinion here. Initially, the activation/deactivation was
created for the baseline topology designed for cases with native
persistence. My thinking was that the mechanism itended to prevent data
inconsistencies while nodes with data on the disk will be in the process of
joining the cl
Denis A. Magda created IGNITE-12615:
---
Summary: Add warning that cluster deactivation purges data from
memory
Key: IGNITE-12615
URL: https://issues.apache.org/jira/browse/IGNITE-12615
Project: Ignite
Vladimir,
In theory, we can add node filter for the corresponding atomics system
cache in AtomicConfiguration. In practice, I do not see how this is useful
unless you limit the node filter to a single node. A lock/semaphore is
represented by a single cache key, so it cannot be collocated with more
Folks, who knows if there are restrictions to add node filter for
distributed Semaphore/Lock? I want to suggest this feature.
I met a case in personal experience: some grid services were filtered by
nodes and launched over a logical sub-cluster. The services worked with
caches being held in the sa
//Got a connectionConnection conn = ...;
//execute() - is just a helper function. Creates prepared statement, pass
params...
//Get all the tables
List> lst = execute(conn, "select SCHEMA_NAME, TABLE_NAME from
SYS.TABLES");
for( List row : lst ){
String schemaName = (String)row.get(0);
Go for it, Vladimir!
> 31 янв. 2020 г., в 16:15, Vladimir Steshin написал(а):
>
> Hi folks. I created a ticket for this (IGNITE-12614):
>
>
>
>
>
> Currently, anyone is able to silently deactivate cluster with command line
> utility (control.sh). Probably with JMX too. Same for the API:
Hi folks. I created a ticket for this (IGNITE-12614):
Currently, anyone is able to silently deactivate cluster with command line
utility (control.sh). Probably with JMX too. Same for the API: Java API –
Ignite.cluster.state(). That would lead to data loss when the persistence
is off. In-me
Vladimir Steshin created IGNITE-12614:
-
Summary: Disallow silent deactivation of cluster to prevent in-mem
data loss.
Key: IGNITE-12614
URL: https://issues.apache.org/jira/browse/IGNITE-12614
Proj
Hi, everyone! I have a question about the following task:
https://issues.apache.org/jira/browse/IGNITE-11663.
The description is not quite concrete, so I want to clarify requirements.
Currently, there are
“internal.processors.cache.persistence.wal.record.RecordTypes.java” class,
which contains
Vasiliy Sisko created IGNITE-12613:
--
Summary: Scala (Visor Console) test failed on Java 8+
Key: IGNITE-12613
URL: https://issues.apache.org/jira/browse/IGNITE-12613
Project: Ignite
Issue Typ
Both issues are related to "compact footer".
https://issues.apache.org/jira/browse/IGNITE-10960 is about comparison
equal objects with and without compact footer.
https://issues.apache.org/jira/browse/IGNITE-12003 is about binary
metadata retrieval by thin client for objects with compact footer.
For me it looks like some coincidence effect. I understand that we get
such behavior because deactivation works the same way as for
persistent caches. Was cluster activation/deactivation designed and
described for in-memory caches? Current behavior sounds for me a as
big risk. I expect a lot of ups
Denis Chudov created IGNITE-12612:
-
Summary: Failing test
IoStatisticsBasicIndexSelfTest.testMetricRegistryRemovedOnIndexDrop after
IGNITE-12496
Key: IGNITE-12612
URL: https://issues.apache.org/jira/browse/IGNITE
IgnitePdsDestroyCacheTest* failures are related to test misconfiguration.
I'll fix it soon.
пт, 31 янв. 2020 г. в 02:56, :
> 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 gra
Hi!
It is proposed to use the same annotation(RepositoryConfig). But value of
field "cacheName" can be constant or Spring EL expression.
Correct cases are:
1) By Spring EL expression
@Repository
@RepositoryConfig(cacheName = "@cacheNames.calendarCacheName")
public interface CalendarRepository ext
Sergey,
Supporting SpEL sounds quite good. Just out of curiosity, how are you
going to evaluate SpEL from a custom annotation?
P.S. I noticed al least 3 mail threads with a name "[IGNITE-12582]
Configuration by property". Please keep the discussion in the same
mail thread.
чт, 30 янв. 2020 г. в
Should not we have the same rights as for main Ignite tests [1]?
[1] https://ci.ignite.apache.org/project/IgniteTests24Java8?mode=trends
чт, 30 янв. 2020 г. в 11:47, Nikolay Izhikov :
>
> I don’t have permissions for this project.
>
> Please, give me admin access for it.
> I want to setup tests f
Vladimir,
I will try to shed a light on this.
1. Statically configured tables in caches (QueryEntity) by default
resides in a schema having the same name as a cache it belongs to
("default" is a cache and a schema name for a table Person in your
example).
2. As you might know SQL literals are case
23 matches
Mail list logo
