Re: Support for Java records in cache

[Humphrey Lopez]

We have faced the same yesterday, I’m also curious if that will be supported in 
the future.

Humphrey 

> On 11 Apr 2024, at 20:12, Victor  wrote:
> 
> Hi
> 
> Using Ignite 2.16, it seems that it's unsupported yet to have a cache of 
> record classes. If so, two questions:
> 
> - is there ETA to support this out-of-the box?
> 
> - there's related github issue https://github.com/apache/ignite/issues/10846, 
> but how can I re-use this code -- not clear which Ignite API this code should 
> be using.
> 
> Thanks,
> 
> Victor
> 

Re: ignitevisorcmd tool - alternate option

[Николай Ижиков]

> Thanks for your email, able to get a list of caches like list . but the 
> result format is not easy to understand. output.txt

Then view output.txt with the any editor, disable wrap lines option.



> 15 апр. 2024 г., в 19:25, Stephen Darlington  
> написал(а):
> 
> What tool are you using?
> 
> If you're using sqlline, you could do "!set output vertical" or only select 
> the columns you're interested in.
> 
> On Mon, 15 Apr 2024 at 17:09, Charlin S  wrote:
> Hello Nizhikov,
> Thanks for your email, able to get a list of caches like list . but the 
> result format is not easy to understand.
> 
> 
> Thanks & Regards,
> Charlin
> 
> 
> On Mon, 15 Apr 2024 at 19:39, Николай Ижиков  wrote:
> Hello, Charlin
> 
> Looks like system view CACHES can help you.
> https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#caches
> 
> 
> > 15 апр. 2024 г., в 09:30, Charlin S  написал(а):
> > 
> > Hi All,
> > Thank you for your email.
> > Still I am missing cache -scan result details like below (in visorcmd). 
> > 
> >  Is it possible to get results using   --cache scan list .   ?
> > 
> > Thanks & Regards,
> > Charlin
> > 
> > 
> > 
> > On Fri, 12 Apr 2024 at 18:46, Николай Ижиков  wrote:
> > Hello, Charlin
> > 
> > Please, take a look at system views:
> > 
> > NODES, BASELINE_NODES.
> > 
> > You can query them by control.sh - 
> > 
> > https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
> > 
> > control.sh --system-view nodes
> > 
> > 
> > > 12 апр. 2024 г., в 15:38, Charlin S  написал(а):
> > > 
> > > Hi Pavel,
> > > Thank you for your email. --baseline argument not showing client node 
> > > list, actually 1 server and 1 client node should shown
> > > 
> > > 
> > > 
> > > Thanks & Regards,
> > > Charlin
> > > 
> > > 
> > > 
> > > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn  wrote:
> > > control.sh is the replacement:
> > > https://ignite.apache.org/docs/latest/tools/control-script
> > > 
> > > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah  
> > > wrote:
> > > Hi Charlin,
> > > 
> > > I am working as a Principal Architect at GridGain.
> > > Let me know if you would like to have a call to discuss your project and 
> > > needs, so I can figure out how to help you.
> > > 
> > > Regards,
> > > Rajiv Shah
> > > 
> > > On Wed, Apr 10, 2024 at 8:01 AM Charlin S  wrote:
> > > Hi All,
> > > Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16 and 
> > > found that 
> > > ignitevisorcmd  tool had been removed from Ignite 2.15 onwards. What is 
> > > the alternative way for checking grids statistics and cache details 
> > > without ignitevisorcmd tool.
> > > 
> > > Thanks & Regards,
> > > Charlin
> > > 
> > 
> 

Re: ignitevisorcmd tool - alternate option

[Stephen Darlington]

What tool are you using?

If you're using sqlline, you could do "!set output vertical" or only select
the columns you're interested in.

On Mon, 15 Apr 2024 at 17:09, Charlin S  wrote:

> Hello Nizhikov,
> Thanks for your email, able to get a list of caches like list . but the
> result format is not easy to understand.
> [image: image.png]
>
> Thanks & Regards,
> Charlin
>
>
> On Mon, 15 Apr 2024 at 19:39, Николай Ижиков  wrote:
>
>> Hello, Charlin
>>
>> Looks like system view CACHES can help you.
>>
>> https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#caches
>>
>>
>> > 15 апр. 2024 г., в 09:30, Charlin S 
>> написал(а):
>> >
>> > Hi All,
>> > Thank you for your email.
>> > Still I am missing cache -scan result details like below (in visorcmd).
>> > 
>> >  Is it possible to get results using   --cache scan list .   ?
>> >
>> > Thanks & Regards,
>> > Charlin
>> >
>> >
>> >
>> > On Fri, 12 Apr 2024 at 18:46, Николай Ижиков 
>> wrote:
>> > Hello, Charlin
>> >
>> > Please, take a look at system views:
>> >
>> > NODES, BASELINE_NODES.
>> >
>> > You can query them by control.sh -
>> >
>> >
>> https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
>> >
>> > control.sh --system-view nodes
>> >
>> >
>> > > 12 апр. 2024 г., в 15:38, Charlin S 
>> написал(а):
>> > >
>> > > Hi Pavel,
>> > > Thank you for your email. --baseline argument not showing client node
>> list, actually 1 server and 1 client node should shown
>> > >
>> > > 
>> > >
>> > > Thanks & Regards,
>> > > Charlin
>> > >
>> > >
>> > >
>> > > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn 
>> wrote:
>> > > control.sh is the replacement:
>> > > https://ignite.apache.org/docs/latest/tools/control-script
>> > >
>> > > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah 
>> wrote:
>> > > Hi Charlin,
>> > >
>> > > I am working as a Principal Architect at GridGain.
>> > > Let me know if you would like to have a call to discuss your project
>> and needs, so I can figure out how to help you.
>> > >
>> > > Regards,
>> > > Rajiv Shah
>> > >
>> > > On Wed, Apr 10, 2024 at 8:01 AM Charlin S 
>> wrote:
>> > > Hi All,
>> > > Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16
>> and found that
>> > > ignitevisorcmd  tool had been removed from Ignite 2.15 onwards. What
>> is the alternative way for checking grids statistics and cache details
>> without ignitevisorcmd tool.
>> > >
>> > > Thanks & Regards,
>> > > Charlin
>> > >
>> >
>>
>>

Re: ignitevisorcmd tool - alternate option

[Николай Ижиков]

Hello, Charlin

Looks like system view CACHES can help you.
https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#caches


> 15 апр. 2024 г., в 09:30, Charlin S  написал(а):
> 
> Hi All,
> Thank you for your email.
> Still I am missing cache -scan result details like below (in visorcmd). 
> 
>  Is it possible to get results using   --cache scan list .   ?
> 
> Thanks & Regards,
> Charlin
> 
> 
> 
> On Fri, 12 Apr 2024 at 18:46, Николай Ижиков  wrote:
> Hello, Charlin
> 
> Please, take a look at system views:
> 
> NODES, BASELINE_NODES.
> 
> You can query them by control.sh - 
> 
> https://ignite.apache.org/docs/latest/tools/control-script#system-view-command
> 
> control.sh --system-view nodes
> 
> 
> > 12 апр. 2024 г., в 15:38, Charlin S  написал(а):
> > 
> > Hi Pavel,
> > Thank you for your email. --baseline argument not showing client node list, 
> > actually 1 server and 1 client node should shown
> > 
> > 
> > 
> > Thanks & Regards,
> > Charlin
> > 
> > 
> > 
> > On Wed, 10 Apr 2024 at 18:40, Pavel Tupitsyn  wrote:
> > control.sh is the replacement:
> > https://ignite.apache.org/docs/latest/tools/control-script
> > 
> > On Wed, Apr 10, 2024 at 3:56 PM Rajiv Shah  wrote:
> > Hi Charlin,
> > 
> > I am working as a Principal Architect at GridGain.
> > Let me know if you would like to have a call to discuss your project and 
> > needs, so I can figure out how to help you.
> > 
> > Regards,
> > Rajiv Shah
> > 
> > On Wed, Apr 10, 2024 at 8:01 AM Charlin S  wrote:
> > Hi All,
> > Currently I am using Ignite 2.10 and planning to upgrade Ignite 2.16 and 
> > found that 
> > ignitevisorcmd  tool had been removed from Ignite 2.15 onwards. What is the 
> > alternative way for checking grids statistics and cache details without 
> > ignitevisorcmd tool.
> > 
> > Thanks & Regards,
> > Charlin
> > 
> 

Re: Question regarding text search in ignite

[Pavel Tupitsyn]

Hi Satyajit, we (Ignite community members) are subscribed to Stackoverflow
too. I don't have anything to add to the existing answer there.

On Mon, Apr 15, 2024 at 8:09 AM  wrote:

> Hi  Pavel/Team,
>
>
>
> Is the  below  explanation  holds  good  from  your  side. Need some
> confirmation on  highlighted  line in  yellow.  We  are  not  using
> Native  persistence.  Our cluster is  in  memory  with  external  cache
> store enabled.
>
>
>
>
> https://stackoverflow.com/questions/70232020/ignite-search-query-not-returning-results-after-cluster-restart-with-native-pers
>
>
>
>
>
>
>
> UPD: in case of configured backups for a partitioned cache it should work
> as a regular index. For example if you add an additional node to the
> baseline topology you would see a rebalance
>  
> happening.
> Rebalance uses regular cache operations to insert entries. Lucene index
> would be built
> 
>  on
> the new node. On the contrary if you remove a node from a cluster you
> would still have a full copy of data including text indexes.
>
>
>
> Regards
>
> Satyajit
>
>
>
>
>
> Barclays Execution Services Limited registered in England. Registered No.
> 1767980. Registered office: 1 Churchill Place, London, E14 5HP
>
> Barclays Execution Services Limited provides support and administrative
> services across Barclays group. Barclays Execution Services Limited is an
> appointed representative of Barclays Bank UK plc, Barclays Bank plc and
> Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays
> Bank plc are authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. Clydesdale Financial Services Limited is authorised and
> regulated by the Financial Conduct Authority.
>
> This email and any attachments are confidential and intended solely for
> the addressee and may also be privileged or exempt from disclosure under
> applicable law. If you are not the addressee, or have received this email
> in error, please notify the sender and immediately delete it and any
> attachments from your system. Do not copy, use, disclose or otherwise act
> on any part of this email or its attachments.
>
> Internet communications are not guaranteed to be secure or virus-free. The
> Barclays group does not accept responsibility for any loss arising from
> unauthorised access to, or interference with, any internet communications
> by any third party, or from the transmission of any viruses. Replies to
> this email may be monitored by the Barclays group for operational or
> business reasons.
>
> Any opinion or other information in this email or its attachments that
> does not relate to the business of the Barclays group is personal to the
> sender and is not given or endorsed by the Barclays group.
>
> Unless specifically indicated, this e-mail is not an offer to buy or sell
> or a solicitation to buy or sell any securities, investment products or
> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays.
>