Good catch Steve ! I also think about that.
Ticket unassigned — you can proceed with it.
Also you need to ask your jira account for granting rights for further ticket
assignation.
High level review can make i (@zstan) and probably (@ivandasch).
Also you need to explain how to run new
Hello igniters,
while I would like to help on the calcite because H2 optimiser (or the lack
thereof) is really killing us, I think that it would be wiser to start by
contributing on something easier.
Therefore I will tackle another problem that we have which is the memory
consumption. I stumbled
Roman Kondakov created IGNITE-13030:
---
Summary: Calcite integration. Push projections to scans and avoid
reading full row when possible
Key: IGNITE-13030
URL: https://issues.apache.org/jira/browse/IGNITE-13030
Denis A. Magda created IGNITE-13029:
---
Summary: Support Spring Data repositories initialization with
Spring Boot auto-starter
Key: IGNITE-13029
URL: https://issues.apache.org/jira/browse/IGNITE-13029
Denis A. Magda created IGNITE-13028:
---
Summary: Spring Data integration doesn't introspect the fields of
the key object
Key: IGNITE-13028
URL: https://issues.apache.org/jira/browse/IGNITE-13028
Roman Kondakov created IGNITE-13027:
---
Summary: Calcite integration. Query parallelism support.
Key: IGNITE-13027
URL: https://issues.apache.org/jira/browse/IGNITE-13027
Project: Ignite
+1
пн, 18 мая 2020 г. в 21:26, Andrey Mashenkov :
> +1
>
> On Mon, May 18, 2020 at 9:19 PM Ivan Rakov wrote:
>
> > Hi Igniters,
> >
> > I have a very simple proposal. Let's set default TX timeout to 5 minutes
> > (right now it's 0 = no timeout).
> > Pros:
> > 1. Deadlock detection procedure is
Roman Kondakov created IGNITE-13026:
---
Summary: Calcite integration. Fix metadata for IgniteTable when it
has embedded filters.
Key: IGNITE-13026
URL: https://issues.apache.org/jira/browse/IGNITE-13026
Roman Kondakov created IGNITE-13025:
---
Summary: Calcite integration. Limit and offset support.
Key: IGNITE-13025
URL: https://issues.apache.org/jira/browse/IGNITE-13025
Project: Ignite
+1
On Mon, May 18, 2020 at 9:19 PM Ivan Rakov wrote:
> Hi Igniters,
>
> I have a very simple proposal. Let's set default TX timeout to 5 minutes
> (right now it's 0 = no timeout).
> Pros:
> 1. Deadlock detection procedure is triggered on timeout. In case user will
> get into key-level deadlock,
+1 here.
Hi Igniters,
I have a very simple proposal. Let's set default TX timeout to 5 minutes
(right now it's 0 = no timeout).
Pros:
1. Deadlock detection procedure is triggered on timeout. In case user
will
get into key-level deadlock, he'll be able to discover root cause from
the
logs
Roman Kondakov created IGNITE-13024:
---
Summary: Calcite integration. Support and simplification of
complex expressions in index conditions
Key: IGNITE-13024
URL:
Hi Ivan,
Support this idea in general but why 5 minutes and not less?
-
Denis
On Mon, May 18, 2020 at 11:19 AM Ivan Rakov wrote:
> Hi Igniters,
>
> I have a very simple proposal. Let's set default TX timeout to 5 minutes
> (right now it's 0 = no timeout).
> Pros:
> 1. Deadlock detection
Hi Igniters,
I have a very simple proposal. Let's set default TX timeout to 5 minutes
(right now it's 0 = no timeout).
Pros:
1. Deadlock detection procedure is triggered on timeout. In case user will
get into key-level deadlock, he'll be able to discover root cause from the
logs (even though load
Roman Kondakov created IGNITE-13023:
---
Summary: Calcite integration. Page scan support.
Key: IGNITE-13023
URL: https://issues.apache.org/jira/browse/IGNITE-13023
Project: Ignite
Issue Type:
Roman Kondakov created IGNITE-13022:
---
Summary: Calcite integration. Merge index conditions for the same
field.
Key: IGNITE-13022
URL: https://issues.apache.org/jira/browse/IGNITE-13022
Project:
Roman Kondakov created IGNITE-13021:
---
Summary: Calcite integration. Avoid full scans for disjunctive
queries.
Key: IGNITE-13021
URL: https://issues.apache.org/jira/browse/IGNITE-13021
Project:
Users shouldn't care about binary_meta and marshaller directories. Those
are internal details. Having to go through the documentation on those
things to figure out whether you need to run each of the provided scripts
or not will lead to terrible user experience.
If we add the
My env:
with 3 VM hosts, say
node1(192.168.1.11)/node2(192.168.1.13)/node3(192.168.1.13).
all 3 nodes run with docker ignite:latest (2.8.0), with --net=host
parameter, zookeeper 3.5.5 runs at node1 with 2181 port;
I have more two components from libs/optional to libs folder, both are
JiajunYang created IGNITE-13020:
---
Summary: Schema change operation failed: Thread got interrupted
while trying to acquire table lock.
Key: IGNITE-13020
URL: https://issues.apache.org/jira/browse/IGNITE-13020
Hello!
> Caused by: org.apache.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode = ConnectionLoss for /apacheIgnite
I guess this is not so much a question for Apache Ignite mailing list than
for ZooKeeper.
Is the Zk cluster alive? Does it respond on that port?
Regards,
--
Hi Alex,
Thanks for starting this thread.
I've created the IEP some time ago but then got distracted by other things.
My thoughts:
*1. Create service proxy on each invoke request*
Single client operation is a lot simpler to implement on both sides (client
and server), so I would prefer this
Stanilovsky Evgeny created IGNITE-13019:
---
Summary: Erroneous join result
Key: IGNITE-13019
URL: https://issues.apache.org/jira/browse/IGNITE-13019
Project: Ignite
Issue Type: Bug
Hello Igniters,
I have plans to implement service invocation in thin clients. I've already
implemented a PoC for java thin client and want to discuss some details.
Also, Pavel Tupitsin has created IEP [1] and the ticket for .Net thin
client [2].
To invoke the service method by java thick client
My env:
with 3 VM hosts, say
node1(192.168.1.11)/node2(192.168.1.13)/node3(192.168.1.13).
all 3 nodes run with docker ignite:latest (2.8.0), with --net=host
parameter, zookeeper 3.5.5 runs at node1 with 2181 port;
I have more two components from libs/optional to libs folder, both are
Hi Konstantin,
Surprisingly, I found your message in a Spam folder (gmail).
We had discussions about the subject before. The most recent one and
reflecting a current state is [1]. You can find many thoughts and
arguments in another discussion [2] (it might be better to start
reading from a
26 matches
Mail list logo
