Re: Welcome message and contribution request
Gotcha. You're added to wiki. - Denis On Fri, Mar 12, 2021 at 11:04 AM Alexander Polovtcev < alexpolovt...@gmail.com> wrote: > No, I'm not planning on documentation contributions only, so thanks for > adding me to the contributors list! I was simply reading this page and I > think I can help with improving it a little bit. Here is my Wiki username: > *apolovtcev* > > On Fri, Mar 12, 2021 at 4:26 PM Denis Magda wrote: > > > Hi Alexander, > > > > Welcome! Are you planning to focus on documentation contributions? How > > frequently do you think you'll be able to do that? > > > > I need to know your Ignite Wiki account to give permissions for editing > > that page. > > > > In the meantime, I used your JIRA id and added to the contributors' list > in > > Ignite JIRA. > > > > > > - > > Denis > > > > > > On Fri, Mar 12, 2021 at 5:08 AM Alexander Polovtcev < > > alexpolovt...@gmail.com> > > wrote: > > > > > Hello everyone! My name is Aleksandr and I would like to contribute to > > > Ignite. I would like to start by updating the following page: > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/TCP+Discovery+SPI+under+the+hood > > > , > > > mostly for correcting typos and grammar. What is the correct process to > > do > > > that? > > > > > > With regards, > > > Aleksandr Polovtcev > > > > > > > > -- > With regards, > Aleksandr Polovtcev >
[jira] [Created] (IGNITE-14310) Update CREATE TABLE, Schema, and Indexing sections
Nikita Safonov created IGNITE-14310: --- Summary: Update CREATE TABLE, Schema, and Indexing sections Key: IGNITE-14310 URL: https://issues.apache.org/jira/browse/IGNITE-14310 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Nikita Safonov See the following discussion: https://lists.apache.org/thread.html/r65e9a7afb36ee11e3d715c57242bb448d0df8d469c44707bcec71875%40%3Cdev.ignite.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Welcome message and contribution request
No, I'm not planning on documentation contributions only, so thanks for adding me to the contributors list! I was simply reading this page and I think I can help with improving it a little bit. Here is my Wiki username: *apolovtcev* On Fri, Mar 12, 2021 at 4:26 PM Denis Magda wrote: > Hi Alexander, > > Welcome! Are you planning to focus on documentation contributions? How > frequently do you think you'll be able to do that? > > I need to know your Ignite Wiki account to give permissions for editing > that page. > > In the meantime, I used your JIRA id and added to the contributors' list in > Ignite JIRA. > > > - > Denis > > > On Fri, Mar 12, 2021 at 5:08 AM Alexander Polovtcev < > alexpolovt...@gmail.com> > wrote: > > > Hello everyone! My name is Aleksandr and I would like to contribute to > > Ignite. I would like to start by updating the following page: > > > > > https://cwiki.apache.org/confluence/display/IGNITE/TCP+Discovery+SPI+under+the+hood > > , > > mostly for correcting typos and grammar. What is the correct process to > do > > that? > > > > With regards, > > Aleksandr Polovtcev > > > -- With regards, Aleksandr Polovtcev
[jira] [Created] (IGNITE-14309) Document snapshot check command
Maxim Muzafarov created IGNITE-14309: Summary: Document snapshot check command Key: IGNITE-14309 URL: https://issues.apache.org/jira/browse/IGNITE-14309 Project: Ignite Issue Type: Bug Components: documentation Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.11 The changes related to the checking snapshot via the command line must be well documented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14308) IgnitePeerToPeerClassLoadingException: Could not use deployment to prepare deployable, because local node id does not correspond with class loader id
Ilya Kasnacheev created IGNITE-14308:
Summary: IgnitePeerToPeerClassLoadingException: Could not use
deployment to prepare deployable, because local node id does not correspond
with class loader id
Key: IGNITE-14308
URL: https://issues.apache.org/jira/browse/IGNITE-14308
Project: Ignite
Issue Type: Bug
Components: binary
Reporter: Ilya Kasnacheev
Assignee: Ilya Kasnacheev
Fix For: 2.11
After IGNITE-12760, the following exception is seen:
{code}
IgnitePeerToPeerClassLoadingException
at
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.checkDeploymentIsCorrect(GridCacheDeploymentManager.java:717)
at
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.prepare(GridCacheDeploymentManager.java:693)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:1213)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1245)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.proceedPrepare(GridNearOptimisticTxPrepareFuture.java:570)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepareSingle(GridNearOptimisticTxPrepareFuture.java:381)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare0(GridNearOptimisticTxPrepareFuture.java:324)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFutureAdapter.prepareOnTopology(GridNearOptimisticTxPrepareFutureAdapter.java:204)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFutureAdapter.prepare(GridNearOptimisticTxPrepareFutureAdapter.java:128)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareNearTxLocal(GridNearTxLocal.java:3965)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitNearTxLocalAsync(GridNearTxLocal.java:4013)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.optimisticPutFuture(GridNearTxLocal.java:2958)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAllAsync0(GridNearTxLocal.java:1033)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.invokeAsync(GridNearTxLocal.java:540)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$27.op(GridCacheAdapter.java:2389)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$27.op(GridCacheAdapter.java:2385)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:3830)
... 29 more
{code}
Turns out, sometimes local deployment belongs to other node id (previous
client?). Changing behavior for local deployments was not anticipated. Let's
change this error to warning for local deployments.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: Welcome message and contribution request
Hi Alexander, Welcome! Are you planning to focus on documentation contributions? How frequently do you think you'll be able to do that? I need to know your Ignite Wiki account to give permissions for editing that page. In the meantime, I used your JIRA id and added to the contributors' list in Ignite JIRA. - Denis On Fri, Mar 12, 2021 at 5:08 AM Alexander Polovtcev wrote: > Hello everyone! My name is Aleksandr and I would like to contribute to > Ignite. I would like to start by updating the following page: > > https://cwiki.apache.org/confluence/display/IGNITE/TCP+Discovery+SPI+under+the+hood > , > mostly for correcting typos and grammar. What is the correct process to do > that? > > With regards, > Aleksandr Polovtcev >
Re: Review Request: IGNITE-8635: Add a Method to Inspect BinaryObject Size
Gentle ping On Thu, 11 Mar 2021 at 2:56 PM, Atri Sharma wrote: > Hi All, > > I have raised a PR for the above mentioned issue. Please see and help > review: > > https://github.com/apache/ignite/pull/8868 > > Regards, > > Atri > > -- > Regards, > > Atri > Apache Concerted > -- Regards, Atri Apache Concerted
Re: Welcome message and contribution request
Sorry, I forgot to include my JIRA username, here it is: apolovtcev With regards, Aleksandr Polovtcev On Fri, Mar 12, 2021 at 2:07 PM Alexander Polovtcev wrote: > Hello everyone! My name is Aleksandr and I would like to contribute to > Ignite. I would like to start by updating the following page: > https://cwiki.apache.org/confluence/display/IGNITE/TCP+Discovery+SPI+under+the+hood, > mostly for correcting typos and grammar. What is the correct process to do > that? > > With regards, > Aleksandr Polovtcev >
Re: IEP-54: Schema-first approach for 3.0
Andrey, What about corresponding async APIs, do we add them now or later? On Thu, Mar 11, 2021 at 8:11 PM Andrey Mashenkov wrote: > Hi Igniters. > > I've created a PR for Table access API [1]. > This is an initial version. So, any suggestions\objections are welcomed. > Please, do not hesitate to write your comments and\or examples to the PR. > > Ignite-api module contains API classes, e.g. TableView classes as > projections for a table for different purposes. > Ignite-table contains dummy implementation and Example class explained how > it is supposed to be used. > > > Also, I'm still waiting for any feedback for Schema configuration public > API PR [2]. > > [1] https://github.com/apache/ignite-3/pull/33 > [2] https://github.com/apache/ignite-3/pull/2 > > On Wed, Jan 20, 2021 at 6:05 PM Andrey Mashenkov < > andrey.mashen...@gmail.com> > wrote: > > > > > I've updated a PR regarding your feedback [1]. > > > > [1] https://github.com/apache/ignite-3/pull/2 > > > > On Mon, Jan 11, 2021 at 10:58 AM Alexey Goncharuk < > > alexey.goncha...@gmail.com> wrote: > > > >> Folks, > >> > >> I updated the IEP to contain the missing pieces; actually, most of the > >> questions here were covered by the text. Please let me know if there is > >> something still missing or unclear. > >> > >> чт, 31 дек. 2020 г. в 12:48, Alexey Goncharuk < > alexey.goncha...@gmail.com > >> >: > >> > >> > Mikhail and Igniters, > >> > > >> > Thanks for your comments. The questions are reasonable, though I think > >> all > >> > concerns are addressed by the IEP as Val mentioned. I will update the > >> > document according to your questions in the following week or so, so > we > >> can > >> > have a constructive discussion further. > >> > > >> > ср, 30 дек. 2020 г. в 11:45, Michael Cherkasov < > >> > michael.cherka...@gmail.com>: > >> > > >> >> Hi Val, Andrey, > >> >> > >> >> thank you for clarifying. > >> >> > >> >> I still have a few comments. > >> >> > >> >> 1. one table == one schema. KV vs SQL: > >> >> Looks like all agreed that KV is just a special case of a regular > table > >> >> with (blob,blob) schema. > >> >> I worry about the case when the user starts from KV case and later > will > >> >> try > >> >> to expand it and try to leverage SQL for the existing KV table it > >> won't be > >> >> able to do so and will require to reload data. which isn't convenient > >> and > >> >> sometimes not even possible. Is it possible to extract a new field > from > >> >> (blob, blob) schema and apply index on it? > >> >> > >> >> 2. Could you please also list all ways of schema definition in the > >> IEP? It > >> >> significant change and I bet the main point of this IEP, everyone > hates > >> >> QueryEntities, they are difficult to manage and in general, it's very > >> >> confusing to have a data model(schemas) and node/cluster > configuration > >> in > >> >> one place. > >> >> > >> >> So there will be SchemaBuilder and SQL to define schemas, but Andrey > >> also > >> >> mentioned annotations. > >> >> > >> >> I personally against configuration via annotations, while it's > >> convenient > >> >> for development, it difficult to manage because different classes can > >> be > >> >> deployed on different clients/servers nodes and it can lead to > >> >> unpredictable results. > >> >> > >> >> 3. IEP doesn't mention field type changes, only drop/add fields. > Field > >> >> type > >> >> changes are extremely painful right now(if even possible), so it > would > >> be > >> >> nice if some scenarios would be supported(like int8->int16, or > >> >> int8->String). > >> >> > >> >> 4. got it, I thought IEP will have more details about the > >> implementation. > >> >> I've seen Andrey even sent benchmark results for a new serialization, > >> will > >> >> ping him about this. > >> >> > >> >> 5. Thanks for the clarification. I had a wrong understanding of > strick > >> >> mode. > >> >> > >> >> > >> >> вт, 29 дек. 2020 г. в 19:32, Valentin Kulichenko < > >> >> valentin.kuliche...@gmail.com>: > >> >> > >> >> > Hi Mike, > >> >> > > >> >> > Thanks for providing your feedback. Please see my comments below. > >> >> > > >> >> > I would also encourage you to go through the IEP-54 [1] - it has a > >> lot > >> >> of > >> >> > detail on the topic. > >> >> > > >> >> > [1] > >> >> > > >> >> > > >> >> > >> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach > >> >> > > >> >> > -Val > >> >> > > >> >> > On Mon, Dec 28, 2020 at 11:22 PM Michael Cherkasov < > >> >> > michael.cherka...@gmail.com> wrote: > >> >> > > >> >> > > Hi all, > >> >> > > > >> >> > > I reviewed the mail thread and proposal page and I still don't > >> fully > >> >> > > understand what is going to be changed, I would really appreciate > >> it > >> >> if > >> >> > you > >> >> > > will answer a few questions: > >> >> > > > >> >> > > 1. Are you going to leave only one schema per cache? if so, will > be > >> >> there > >> >> > > an option to have a table with arbitrary objects(pure KV case)
Re: Ignite contributing
Hello, Please see [1], [2]. In short: * Create a JIRA account and ask for Contributor permissions here on the dev list * Pick a ticket, implement, ask for review (by mentioning maintainers [3] in the ticket or here) [1] https://ignite.apache.org/community/contribute.html [2] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute [3] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewProcessandMaintainers On Fri, Mar 12, 2021 at 1:51 PM Константин Потапов < mr.konstantin.pota...@gmail.com> wrote: > Hello, > I would like to contribute to Ignite, what further steps i need to do? >
Welcome message and contribution request
Hello everyone! My name is Aleksandr and I would like to contribute to Ignite. I would like to start by updating the following page: https://cwiki.apache.org/confluence/display/IGNITE/TCP+Discovery+SPI+under+the+hood, mostly for correcting typos and grammar. What is the correct process to do that? With regards, Aleksandr Polovtcev
Ignite contributing
Hello, I would like to contribute to Ignite, what further steps i need to do?
Re: Re[2]: Run sql query on key-value cache
Hello! Yes, it does indeed seem that you can now enable indexing on a cache by doing "CREATE TABLE ... WITH "cache_name="; + dev@ Do we have this documented anywhere? Updating CREATE TABLE docs and Schema and Indexing would be nice. https://ignite.apache.org/docs/latest/SQL/indexes#creating-indexes-with-sql should also refer to CREATE TABLE btw. Regards, -- Ilya Kasnacheev пт, 12 мар. 2021 г. в 13:40, Zhenya Stanilovsky : > Ilya, seems you mistaken, check [1] > Seems there is no additional documentation, but API is simple , check > example [2]. > > [1] https://issues.apache.org/jira/browse/IGNITE-12808 > [2] > https://github.com/apache/ignite/pull/7627/files#diff-d0f1fdd4e070c92459cb4f1e600977bd4819216e658ff2114fe19bfeb2a93232R1000 > > > Hello! > > Once a cache is created, you can't add indexes. You will need to recreate > cache / restart cluster with updated configuration. > > You can define caches with Query Entities in spring XML configuration, > pass it to IgniteConfguration instance. > > Regards, > -- > Ilya Kasnacheev > > пт, 12 мар. 2021 г. в 07:07, rakshita04 >: > > How can we create indexes on our existing cache. > As far as i could see on your portal no API support is available for C++ > for > creating indexes. > does Query Entity automatically takes care of creating indexes? or we need > to explicitly create indexes on our cache? > if we need to explicitly create , can you please help us how to do that? > > regards, > Rakshita Chaudhary > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > > > > > >
