Denis Magda created IGNITE-2359:
---
Summary: Race in MarshallerContextImpl when working with files
that store "id->clsName" mapping
Key: IGNITE-2359
URL: https://issues.apache.org/jira/browse/IGNITE-2359
Valentin Kulichenko created IGNITE-2358:
---
Summary: Write behind store swallows exception trace in case of
error
Key: IGNITE-2358
URL: https://issues.apache.org/jira/browse/IGNITE-2358
Project: I
Nick,
I am still a bit confused. Can you please describe what happens right now
with the image we have stored on the docker hub? I am interested in what
Ignite version is stored there and what Ignite version is downloaded
whenever no specific version is passed.
D.
On Mon, Jan 11, 2016 at 10:26 A
>
> In that case, why does the docker image contain any version of Ignite at
> all?
>
We download docker image which was built from Dockerfile (which contains
specific version of Ignite) and the image contains Ignite distributive.
Apache Ignite distributive is downloaded only once in during the bui
Andrey, I think Cos won’t mind if you will provide a new PR.
On Mon, Jan 11, 2016 at 10:08 AM, Andrey Gura wrote:
> Dmitry,
>
> If I understand correctly this ticket (
> https://issues.apache.org/jira/browse/ZEPPELIN-545) assigned to Cos and
> has
> Fixed status.
>
> The fix is ok. But removing
Nick,
It sounds like we always download a version of ignite, either latest or
provided by user. In that case, why does the docker image contain any
version of Ignite at all?
D.
On Mon, Jan 11, 2016 at 10:08 AM, Nikolay Tikhonov
wrote:
> On Mon, Jan 11, 2016 at 8:39 PM, Dmitriy Setrakyan
> wro
Dmitry,
If I understand correctly this ticket (
https://issues.apache.org/jira/browse/ZEPPELIN-545) assigned to Cos and has
Fixed status.
The fix is ok. But removing of marshaller bean definition is better
solution. So I can provide new PR or we can wait for Cos.
On Mon, Jan 11, 2016 at 8:55 PM
On Mon, Jan 11, 2016 at 8:39 PM, Dmitriy Setrakyan
wrote:
>
>
> I am not sure I understand. Are you suggesting we have different docker
> files for different versions?
Yes, for each Ignite version need to create Dockerfile with version and tag
on DockerHub.
I would prefer that unless a version
Andrey,
Any chance we could upgrade Zeppelin to work with Ignite 1.5?
D.
On Mon, Jan 11, 2016 at 7:44 AM, Andrey Gura wrote:
> Cos,
>
> the problem is that default config
> (incubator-zeppelin/ignite/src/main/resources/default-ignite-jdbc.xml)
> contains `marshaller` bean definition of Optimiz
Nick,
I am not sure I understand. Are you suggesting we have different docker
files for different versions? I would prefer that unless a version is
explicitly specified, the docker file should download the latest version.
Can we update the file on ignite docker hub?
D.
On Mon, Jan 11, 2016 at 7:
Cos,
the problem is that default config
(incubator-zeppelin/ignite/src/main/resources/default-ignite-jdbc.xml)
contains `marshaller` bean definition of OptimizedMarshaller type.
IgniteSqlInterpreter class uses this config.
Just remove this bean definition and default marshaller will be used.
On M
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/395
IGNITE-2350: Make IGNITE_UPDATE_NOTIFIER per cluster setting
https://issues.apache.org/jira/browse/IGNITE-2350
You can merge this pull request into a Git repository by running:
$ git pull htt
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/394
IGNITE-2228 .Net: Ensure async Task can be cancelled.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-2228-1
Alternat
Dima,
Docker hub shows Dockerfile for `1.0.0-incubating` tag [1]. For this tag it
is correct. [2]
I would prefer see Dockerfile for the latest version, but I can't find
functionality to change it. I'll ask DockerHub community how fix it.
1. https://hub.docker.com/r/apacheignite/ignite/~/dockerfile
Cos,
> In JIRA, open tickets are automatically got moved to the next version,
once
> the current one is getting "released" in JIRA, so the reassignment is done
> without any human intervention normally. There's no need for any process
> around it, IIRC.
Agree, but this way you can miss some impor
Hi,
I implemented Apache Ignite (http://ignite.apache.org/) based cluster
manager for Vert.x.
Source code can be found here https://github.com/apacheignite/vertx-ignite
I hope that Vert.x community will review it and include this component into
vert.x stack and move code into new repo under v
As for dynamic caches this is usually ok, because application can use
method getOrCreateCache(). For dynamic indexes probably you don't want to
write all the initialization logic each time client tries to access cache.
Sergi
2016-01-11 14:07 GMT+03:00 Sergi Vladykin :
> I mean it would be quite
I mean it would be quite weird if dynamically created index silently
disappears at some point. This may be obvious for you but not for everyone.
We can start with version which does not persist dynamic configuration but
looking forward it must be designed with persistence in mind. Probably we
can u
Vladimir Ozerov created IGNITE-2357:
---
Summary: IgfsSecondaryFileSystem should be serizliable.
Key: IGNITE-2357
URL: https://issues.apache.org/jira/browse/IGNITE-2357
Project: Ignite
Issue T
Vladimir Ozerov created IGNITE-2356:
---
Summary: IGFS client should be able to failover in case of server
crash.
Key: IGNITE-2356
URL: https://issues.apache.org/jira/browse/IGNITE-2356
Project: Ignite
Vladimir Ozerov created IGNITE-2355:
---
Summary: Hadoop client should be able to failover in case of
server crash.
Key: IGNITE-2355
URL: https://issues.apache.org/jira/browse/IGNITE-2355
Project: Igni
Vladimir Ozerov created IGNITE-2354:
---
Summary: Ensure that Hadoop client is still operational after
failed map-reduce jobs.
Key: IGNITE-2354
URL: https://issues.apache.org/jira/browse/IGNITE-2354
Pr
Sergey,
Correct, thats a backward compatibility fix.
Internal node's version based on maven version but each ".a", ".b" and
".final" replaces with corresponding "-".
On Wed, Jan 6, 2016 at 7:14 AM, Konstantin Boudnik wrote:
> On Tue, Jan 05, 2016 at 08:20PM, Sergey Kozlov wrote:
> > Hi
> >
> >
Vladimir Ozerov created IGNITE-2353:
---
Summary: IGFS and Hadoop clients must be able to failover to other
nodes
Key: IGNITE-2353
URL: https://issues.apache.org/jira/browse/IGNITE-2353
Project: Ignite
Vladimir Ozerov created IGNITE-2352:
---
Summary: IGFS shows incorrect file properties when running over
secondary file system.
Key: IGNITE-2352
URL: https://issues.apache.org/jira/browse/IGNITE-2352
P
Alexey Kuznetsov created IGNITE-2351:
Summary: Rework metadata creation
Key: IGNITE-2351
URL: https://issues.apache.org/jira/browse/IGNITE-2351
Project: Ignite
Issue Type: Sub-task
Yakov Zhdanov created IGNITE-2350:
-
Summary: Make IGNITE_UPDATE_NOTIFIER per cluster setting
Key: IGNITE-2350
URL: https://issues.apache.org/jira/browse/IGNITE-2350
Project: Ignite
Issue Type
Alexey Kuznetsov created IGNITE-2349:
Summary: Rework cache creation
Key: IGNITE-2349
URL: https://issues.apache.org/jira/browse/IGNITE-2349
Project: Ignite
Issue Type: Sub-task
Andrey Gura, can you please clarify?
--Yakov
2016-01-06 22:06 GMT+03:00 Konstantin Boudnik :
> On Tue, Jan 05, 2016 at 10:40PM, Dmitriy Setrakyan wrote:
> > On Tue, Jan 5, 2016 at 8:12 PM, Konstantin Boudnik
> wrote:
> >
> > > Test is pretty simple and doesn't do anything crazy at least in my
>
Alexey Kuznetsov created IGNITE-2348:
Summary: Rework SQL demo
Key: IGNITE-2348
URL: https://issues.apache.org/jira/browse/IGNITE-2348
Project: Ignite
Issue Type: Sub-task
Affects Ver
Alexey Kuznetsov created IGNITE-2347:
Summary: Rework demo for load metadata
Key: IGNITE-2347
URL: https://issues.apache.org/jira/browse/IGNITE-2347
Project: Ignite
Issue Type: Sub-task
31 matches
Mail list logo
