GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/339
IGNITE-2152 .NET: Introduction page is missing.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-2152
Alternatively yo
Ilya Suntsov created IGNITE-2176:
Summary: Not valid exceptions in case when example can't works
with remote node started with server classpath (Java 8)
Key: IGNITE-2176
URL: https://issues.apache.org/jira/browse/
Ilya Suntsov created IGNITE-2175:
Summary: Not valid exceptions in case when example can't works
with remote node started with server classpath (Java 7)
Key: IGNITE-2175
URL: https://issues.apache.org/jira/browse/
Got it. Yakov, I think this will work without any coding change. Can you
confirm?
On Tue, Dec 15, 2015 at 6:30 PM, Alexey Kuznetsov
wrote:
> I think mentioned examples could be easily fixed by switching from use of
> H2 started from example to o.a.i.examples.util.DbH2ServerStartup.
> This will s
Pavel Konstantinov created IGNITE-2174:
--
Summary: Error with owerwrite dialog on loading metadata from DB
Key: IGNITE-2174
URL: https://issues.apache.org/jira/browse/IGNITE-2174
Project: Ignite
I think mentioned examples could be easily fixed by switching from use of
H2 started from example to o.a.i.examples.util.DbH2ServerStartup.
This will start full fledged H2 server with in-memory db and all nodes will
work with it.
>> Ignite nodes, then why not switch to using H2 disk store?
Dima, t
If the problem is the H2 in-memory store not being shared between multiple
Ignite nodes, then why not switch to using H2 disk store?
On Tue, Dec 15, 2015 at 4:11 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> As far as I understand, the issue is that CacheJdbcStoreExample
> and
As far as I understand, the issue is that CacheJdbcStoreExample
and CacheSpringStoreExample use in-memory H2 database, so the cache store
is not shared among nodes. What if we just switch to a file-based DB? It
looks like a simple change to me.
And I would remove CacheDummyStoreExample. It looks w
I think we should fix all the examples. What has changed that makes these
examples so difficult to fix?
I really do not like removing the examples that have been continuously
shipped in every release. If it is so difficult for us to upgrade them to
1.5, how difficult will it be for our users?
D.
Hi, Younggyu Chun.
You should translate the latest version, which is 1.5.
When we move to the next version, you can translate only the changes. All
the documentation changes are recorded in the Ignite Documentation GIT
Repository on GitHub:
https://github.com/apacheignite/documentation
D.
On T
Michael Griggs created IGNITE-2173:
--
Summary: Some log.debug() calls in CacheAbstractJdbcStore.java are
not protected with if (log.isDebugEnabled())
Key: IGNITE-2173
URL: https://issues.apache.org/jira/browse/IGN
Guys,
I've re-checked these examples. Most of the benchmarks corresponding to the
description that was provided by Yakov above but the following examples
don't work with remote nodes started with server classpath :
- org.apache.ignite.examples.datagrid.CacheQueryExample
- org.apache.ignite.e
Raúl Kripalani created IGNITE-2172:
--
Summary: Uneven API between IgniteMessaging#stopRemoteListen and
#stopLocalListen
Key: IGNITE-2172
URL: https://issues.apache.org/jira/browse/IGNITE-2172
Project:
Yakov Zhdanov created IGNITE-2171:
-
Summary: ComputeExecutionRejectedException not handled when
JobStealingCollisionSpi is used
Key: IGNITE-2171
URL: https://issues.apache.org/jira/browse/IGNITE-2171
Yakov Zhdanov created IGNITE-2170:
-
Summary: DHT preloader: response to partitions request may be sent
bypassing waits for ops to finish
Key: IGNITE-2170
URL: https://issues.apache.org/jira/browse/IGNITE-2170
We still have very advanced and cool CacheBinaryAutoStoreExample and it
works properly
--Yakov
2015-12-15 18:11 GMT+03:00 Dmitriy Setrakyan :
> If it is an example issue, why can’t we fix the examples? I am not
> comfortable removing CacheJdbcStoreExample from the release.
>
> On Tue, Dec 15, 20
If it is an example issue, why can’t we fix the examples? I am not
comfortable removing CacheJdbcStoreExample from the release.
On Tue, Dec 15, 2015 at 4:02 AM, Yakov Zhdanov wrote:
> https://issues.apache.org/jira/browse/IGNITE-2158
>
> Guys,
>
> It seems that CacheDummyStoreExample, CacheJdbcS
Michael Griggs created IGNITE-2169:
--
Summary: Ignite-import-schema tool generates incorrect null schema
for JDBC
Key: IGNITE-2169
URL: https://issues.apache.org/jira/browse/IGNITE-2169
Project: Ignit
Hi, Denis,
1) my opinion is that we'd better not mention 'setup-hadoop' script at all
(for the reasons mentioned above) and delete it in the nearest release.
2) Now Ignite is a part of BigTop distribution (see
https://issues.apache.org/jira/browse/IGNITE-665), so the old BigTop
instruction is not r
Hi Vikrant,
Do you have free time to complete the integration in the nearest month?
This integration is becoming quite urgent. So if you don’t have time for now
someone else from the community will pick this ticket up.
Regards,
Denis
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/338
IGNITE-1994 .Net: CrossPlatformExample looks unnecessary
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-1994
Alterna
https://issues.apache.org/jira/browse/IGNITE-2158
Guys,
It seems that CacheDummyStoreExample, CacheJdbcStoreExample and
CacheSpringStoreExample do not work correctly in distributed environment
after code modifications to demonstrate clear() and withSkipStore()
This is an old issue and it is 100%
Github user avinogradovgg closed the pull request at:
https://github.com/apache/ignite/pull/323
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/331
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
/faq.html#noconfig for more
info.
[14:22:00]__
[14:22:00] / _/ ___/ |/ / _/_ __/ __/
[14:22:00] _/ // (7 7// / / / / _/
[14:22:00] /___/\___/_/|_/___/ /_/ /___/
[14:22:00]
[14:22:00] ver. 1.5.0-b2#20151215-sha1:0c550aaa
[14:22:00] 2015 Copyright(
Vladimir Ozerov created IGNITE-2167:
---
Summary: Create cross-platform example
Key: IGNITE-2167
URL: https://issues.apache.org/jira/browse/IGNITE-2167
Project: Ignite
Issue Type: Task
Github user ashutakGG closed the pull request at:
https://github.com/apache/ignite/pull/334
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/337
IGNITE-2164: Added documentation brief description auto generation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-2164
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/336
IGNITE-2159: Implemented 64-bit atomics with supported functions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-2159
Al
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/335
Ignite 2016: Kafka Connect Integration
Kafka Connect is a new standard method "for scalably and reliably streaming
data between Apache Kafka and other systems" from the latest Kafka 0.9.0.
You can
Thanks for the invitation
here is a question. Which version of ignite document should be translated?
2015년 12월 15일 화요일, Dmitriy Setrakyan님이 작성한 메시지:
> Hi, Younggyu Chun!
>
> I have added you to the English documentation project on readme. I have
> also created an empty project for Korean document
Hi Ivan,
Thanks for clarification.
Actually I’ve modified the content of the following pages:
- Added “Atomatic Hadoop Configuration” section that describes the usage of
setup-hadoop with all its pros and cons for Apache Hadoop and CDH
http://apacheignite.gridgain.org/v1.5/docs/installing-on-ap
Vladimir Ozerov created IGNITE-2166:
---
Summary: .NET: Add toBuilder() method on BinaryObject interface.
Key: IGNITE-2166
URL: https://issues.apache.org/jira/browse/IGNITE-2166
Project: Ignite
Hi, Younggyu Chun!
I have added you to the English documentation project on readme. I have
also created an empty project for Korean documentation and sent you an
invite as well.
Give readme a shot and see if you like it. Let me know if you have any
questions.
D.
On Tue, Dec 15, 2015 at 1:09 AM,
Denis, good question.
Yes, there are several reasons.
1) setup-hadoop is suitable for Apache Hadoop distribution, but not for all
others (e.g. BigTop)
2) setup-hadoop rewrites global configs (core-site.xml, mapred-site.xml),
what prevents further cluster usage without Ignite.
3) setup-hadoop needs
hi Dmitriy Setrakyan
readme.io will be good choice
i'm just planning to use the same format as english version documents did
could you please create project in readmeio and give me english version
html for me?
younggyu, chun
2015년 12월 15일 화요일, Dmitriy Setrakyan님이 작성한 메시지:
> Thanks, Younggyu
Igor Sapego created IGNITE-2165:
---
Summary: CPP: Tableu displays textual data in wrong locale.
Key: IGNITE-2165
URL: https://issues.apache.org/jira/browse/IGNITE-2165
Project: Ignite
Issue Type:
Thanks, Younggyu Chun!
This will be a great contribution.
Feel free to choose the format for the documentation. For example, we can
create a project for you in readme.io, like we have for the main Ignite
documentation. Alternatively you may choose to do it directly in MD format,
and then use some
Vladimir Ozerov created IGNITE-2164:
---
Summary: CPP: Namespace/class desciptions are missing in generated
docs.
Key: IGNITE-2164
URL: https://issues.apache.org/jira/browse/IGNITE-2164
Project: Ignite
Igor Sapego created IGNITE-2163:
---
Summary: CPP: ODBC driver supported version should be upgraded to
3.x
Key: IGNITE-2163
URL: https://issues.apache.org/jira/browse/IGNITE-2163
Project: Ignite
Hi Younggyu, Chun!
Thats pretty cool! Thanks a lot for your help!
We already have translation to simplified chinese.
And I think we should do the same for Korean.
Take a look at this thread:
http://apache-ignite-developers.2346864.n4.nabble.com/about-apache-ignite-s-document-localization-Simplif
Dima,
As class can "migrate" between caches, we should have only single write
logic across all caches and nodes. For this reason it is better to place
this flag in BinaryTypeConfiguration.
Regarding OptimizedMarshaller - the sole purpose is consistency. If class
cannot be written with BinaryMarsh
42 matches
Mail list logo
