Alexey Kuznetsov created IGNITE-2161:
Summary: We need to tune Ignite site css to make it looks good for
printing
Key: IGNITE-2161
URL: https://issues.apache.org/jira/browse/IGNITE-2161
Project:
Dear Igniters,
My name is Ilya Lantukh, I am a Java Developer from St. Petersburg, Russia
and I've recently joined the Apache Ignite community.
I hope to find here a lot of opportunities to improve my skills and
knowledge and I wish to be helpful in solving current problems and
developing new
I am ok with the suggestion. Val, can you please file a ticket (or I guess
we already should have one) and put your suggestion to it.
--Yakov
2015-12-14 11:47 GMT+03:00 Valentin Kulichenko <
valentin.kuliche...@gmail.com>:
> Denis,
>
> Yes, this can be a workaround, but at the same time it
Vladimir Ozerov created IGNITE-2153:
---
Summary: .NET: Package descriptions are missing in
doxygen-generated files.
Key: IGNITE-2153
URL: https://issues.apache.org/jira/browse/IGNITE-2153
Project:
Sergey Kozlov created IGNITE-2155:
-
Summary: CacheStarSchemaExample isn't clear and it seems the
output is wrong
Key: IGNITE-2155
URL: https://issues.apache.org/jira/browse/IGNITE-2155
Project:
Github user ashutakGG closed the pull request at:
https://github.com/apache/ignite/pull/329
---
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
Vladimir Ozerov created IGNITE-2152:
---
Summary: .NET: Introduction page is missing.
Key: IGNITE-2152
URL: https://issues.apache.org/jira/browse/IGNITE-2152
Project: Ignite
Issue Type: Bug
Sure,
Will try to finish this by end of this month.
On Dec 14, 2015 3:59 PM, "Denis Magda" wrote:
> Hi Chandresh,
>
> Is there any chance you complete the ticket from the subj during this
> month?
> https://issues.apache.org/jira/browse/IGNITE-429
>
> If you're too busy for
Github user ashutakGG closed the pull request at:
https://github.com/apache/ignite/pull/325
---
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
Welcome, Ilya!
Should you have any questions, feel free to ask here.
Sergi
2015-12-14 12:14 GMT+03:00 Ilya Lantukh :
> Dear Igniters,
>
> My name is Ilya Lantukh, I am a Java Developer from St. Petersburg, Russia
> and I've recently joined the Apache Ignite community.
>
Denis Magda created IGNITE-2156:
---
Summary: .Net: add IgniteClientDisconnectedException to the .Net
API
Key: IGNITE-2156
URL: https://issues.apache.org/jira/browse/IGNITE-2156
Project: Ignite
Pavel Konstantinov created IGNITE-2162:
--
Summary: Add dialect name to property name in 'secret.properties'
file
Key: IGNITE-2162
URL: https://issues.apache.org/jira/browse/IGNITE-2162
Project:
Vova,
I think I am beginning to see your point. However, my concern is that users
may wish to ignore Externalizable and use the Binary protocol. Is it
possible to have a configuration flag on per-cache basis?
Also, why delegate to OptimizedMarshaller for Externalizalbe classes? Can’t
we have
Hi Igniters,
Yes but could please provide a push that includes the ignite osgi stuffs?
Regards,
Romain
Le lun. 14 déc. 2015 à 07:27, Dmitriy Setrakyan a
écrit :
> Igniters,
>
> Since we have releases 1.5-b1, the community has reported several issues,
> which were
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/334
ignite-2065
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashutakGG/incubator-ignite
ignite-2065-requests
Alternatively you can review
On Mon, Dec 14, 2015 at 1:30 AM, Vladimir Ozerov
wrote:
> This doesn't work because there still will be interference between tests
> within the same class.
I agree with Yakov. How about cleaning this marshalling directory right
after the grid stop?Cleaning it more
Ivan, I think this should be documented, no?
On Mon, Dec 14, 2015 at 2:25 AM, Ivan V. wrote:
> To enable just an IGFS persistence there is no need to use HDFS (this
> requires Hadoop dependency, requires configured HDFS cluster, etc.).
> We have requests
Dima,
I do not think it is possible to get list of such classes because this can
be any class from any library. Can you explain what is your concerns?
On Tue, Dec 15, 2015 at 1:46 AM, Dmitriy Setrakyan
wrote:
> Vladimir,
>
> I am not sure I like the approach you are
Dear igniters
I would like to translate the ignite documents in Korean as many Koreans
recently are getting intereted in the ignite project. I introduced
my colleagues to the ignite, and then my colleagues are planning to use the
ignite as shared RDDs for spark and data grid instead of applying
Vasilisa Sidorova created IGNITE-2157:
--
Summary: CacheClientBinaryPutGetExample javadoc should be updated
Key: IGNITE-2157
URL: https://issues.apache.org/jira/browse/IGNITE-2157
Project: Ignite
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/332
Ignite 2100
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agoncharuk/ignite ignite-2100
Alternatively you can review and apply these
Ilya Suntsov created IGNITE-2158:
Summary: Null values in examples output
Key: IGNITE-2158
URL: https://issues.apache.org/jira/browse/IGNITE-2158
Project: Ignite
Issue Type: Bug
Raul,
Tag 1.5.0-b1 fixed, please check.
On Mon, Dec 14, 2015 at 3:59 PM, Raul Kripalani wrote:
> On Mon, Dec 14, 2015 at 10:36 AM, Yakov Zhdanov
> wrote:
>
> > osgi has been pushed to 1.5 after b1 has been built. You can build ignite
> > binaries from
Guys,
There is currently a limitation - we cannot effectively deploy class
definitions over discovery protocol. This is possible to fix, but needs
some more investigation.
As far as current situation with examples, I think that the following
examples should work with remote nodes started with
No, it prints to std or to log with INFO level. Let's postpone this for
now, however, I ask everyone to be attentive and remove debug output on
commit.
--Yakov
2015-12-14 15:46 GMT+03:00 Anton Vinogradov :
> Yakov,
> We can simply grep sources for U.debug(), but I'm
Github user ashutakGG closed the pull request at:
https://github.com/apache/ignite/pull/317
---
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
On Mon, Dec 14, 2015 at 7:28 AM, Denis Magda wrote:
> Yes, this will be documented tomorrow. I want to go though all the steps
> by myself checking all other possible obstacles the user may face with.
>
Thanks, Denis!
>
> —
> Denis
>
> > On 14 дек. 2015 г., at 18:11,
Valentin Kulichenko created IGNITE-2160:
---
Summary: Ignition.start() is blocked if there are no server nodes
Key: IGNITE-2160
URL: https://issues.apache.org/jira/browse/IGNITE-2160
Project:
Yakov,
Here is the ticket: https://issues.apache.org/jira/browse/IGNITE-2160
-Val
On Mon, Dec 14, 2015 at 1:33 AM, Yakov Zhdanov wrote:
> I am ok with the suggestion. Val, can you please file a ticket (or I guess
> we already should have one) and put your suggestion to
Folks,
Currently BinaryMarshaller works in a very non-trivial way:
1) If class is Serializable or Binarylizable, it is written in binary
format and can be used without deserialization.
2) If class implements Externalizable, it is written in binary format, but
without fields metadata.
3) If class
Saikat,
Thanks for fixing this compilation issue. I've merged the changes into
the master.
--
Denis
On 12/13/2015 11:48 AM, samaitra wrote:
GitHub user samaitra opened a pull request:
https://github.com/apache/ignite/pull/326
[Test] IgniteSemaphore's failover related tests are
I am against changing core logic just for test env.
How about cleaning up the disc storage after test class completes?
--Yakov
2015-12-14 10:12 GMT+03:00 Vladimir Ozerov :
> Folks,
>
> As you know our marshallers persists some data to disk. Namely, mappings
> from class
This doesn't work because there still will be interference between tests
within the same class.
Proposed change is minimal. We already have interface - MarshallerContext.
All we need is to create dummy implementation for it and hack a single line
in GridKernalCotextImpl class.
On Mon, Dec 14,
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/330
IGNITE-2138 Introduced toBuilder() method.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agoncharuk/ignite ignite-2138
Alternatively you
Romain,
osgi has been pushed to 1.5 after b1 has been built. You can build ignite
binaries from ignite-1.5 branch to test the functionality.
--Yakov
2015-12-14 12:21 GMT+03:00 Romain Gilles :
> Hi Igniters,
> Yes but could please provide a push that includes the ignite
Guys,
Here is the list of open issues for 1.5
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.5%20AND%20status%20!%3D%20closed%20ORDER%20BY%20status%20DESC%2C%20due%20ASC%2C%20priority%20DESC%2C%20created%20DESC
I see 58 items in this list, however
Guys,
I noticed the following code in repo several days
ago(org/apache/ignite/internal/portable/BinaryWriterExImpl.java:1810):
out.unsafeEnsure(1 + 4);
out.unsafeWriteByte(GridPortableMarshaller.HANDLE);
out.unsafeWriteInt(pos - old);
if (obj.getClass().isArray())
Vasilisa Sidorova created IGNITE-2159:
--
Summary: Platforms examples couldn't be executed under 32-bit OS
Key: IGNITE-2159
URL: https://issues.apache.org/jira/browse/IGNITE-2159
Project: Ignite
Denis, after mvn clean package classnames.properties was not marked as
changed in Idea.
On Mon, Dec 14, 2015 at 2:57 PM, Denis Magda wrote:
> Alex,
>
> Have you updated and pushed classnames.properties? We have to do this
> otherwise the end user will have the same issues
Guys,
Why don't we include ignite-hadoop module in Fabric? This user simply wants
to configure HDFS as a secondary file system to ensure persistence. Not
having the opportunity to do this in Fabric looks weird to me. And actually
I don't think this is a use case for Hadoop Accelerator.
-Val
On
Valya,
Because we decide whether to load Hadoop module based on its availability
in classpath. And when Hadoop module is loaded, certain restrictions are
applied to configuration, e.g. peerClassLoadingEnabled must be false.
All this looks very inconvenient for me, but this is how things currently
Guys,
There is already a configuration property that lets to complete client's
launching procedure even if there is no any server node in a cluster -
TcpDiscoverySpi.setForceServerMode.
The only side effect of this property is that a client node will become
a part of the ring.
Is this
Denis,
Thanks for pointing to this. File rebuilded and pushed to ignite-1.5.
On Mon, Dec 14, 2015 at 3:14 PM, Denis Magda wrote:
> Alex,
>
> Try to build a package and replace classnames.properties located in the
> project with the classnames.properties from your output
Denis,
Yes, this can be a workaround, but at the same time it makes things even
more confusing :) This means that client node behavior depends on
some property on discovery SPI, while this property should influence only
internals of discovery protocol.
I think the client should always work in
GitHub user Dmitriyff opened a pull request:
https://github.com/apache/ignite/pull/328
IGNITE-2147 fixed reload data in ui ace tabs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Dmitriyff/ignite ignite-2147
Alternatively you
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/313
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/242
---
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
47 matches
Mail list logo