Re: [EXTERNAL] Re: Nifi putting object to S3 directory
Hi Natalia,
You can set the "directory" in the Prefix property of ListS3. In this case
no UpdateAttribute is needed, just connect ListS3 -> FetchS3Object.
Regards,
Peter Turcsanyi
On Mon, May 16, 2022 at 4:24 PM Fill, Natalia wrote:
> Hi Nifi Team,
>
> Following from tests below I need to retrieve files from specific
> directories on S3. The files are placed into dir/subdir/.
> I tried various expression to specify 'filename' variable that feeds to
> FetchS3Object and still get error that the key doesn't exist.
> I am not sure if FetchS3Object doesn't like my directories pattern or the
> file name. If I don't specify any pattern and just fetch what was listed,
> it works fine.
> The flow goes as follows: ListS3 (lists all the files as expected) -
> UpdateAttribute (updates filename with the pattern to use) - FetchS3Object
> - LogAttribute on success and on failure.
>
> Some of my tries for filename pattern below:
> *( dir/subdir/test_put_\d*_\d*\.txt).*
> *( test_put_\d*_\d*\.txt).*
> dir/subdir /test_put_\d*_\d*\.txt
> dir/subdir /test_put_${now():format('-MM-dd')}_*
> /dir/subdir /test_put_${now():format('-MM-dd')}_*
>
> List of files on s3 server is like below:
> 2022-05-16 13:36:03 14 test_put_20220516_013601.txt
> 2022-05-16 13:36:04 14 test_put_20220516_013602.txt
>
> Can anyone suggest how do I retrieve files in dir/subdir that start with a
> particular string (e.g. test_put_) contain today's date and end with
> sequence of numbers.
>
> Thanks
> Natalia
>
> .
> -Original Message-
> From: Fill, Natalia
> Sent: 16 May 2022 13:15
> To: dev@nifi.apache.org
> Subject: RE: [EXTERNAL] Re: Nifi putting object to S3 directory
>
> Thanks Peter, removing leading slash worked and now Nifi puts file into
> specified subdirectory.
>
> This is a simple test flow to test read/write to s3: GenerateFlowFile - on
> success - UpdateAttribute (filename to meaningful name) - on success -
> PutS3Object - on success and on failure LogAttribute
>
> Regards
> Natalia
>
> -Original Message-
> From: Peter Turcsanyi
> Sent: 16 May 2022 12:41
> To: dev@nifi.apache.org
> Subject: [EXTERNAL] Re: Nifi putting object to S3 directory
>
> CAUTION: This email originated from outside of the organisation. Do not
> click links or open attachments unless you recognise the sender and know
> the content is safe.
>
>
> Hi Natalia,
>
> Is the FlowFile transferred to the success or the failure relationship
> from PutS3Object?
>
> In general, you need to use dirtag/subdirtag /${filename}, so no leading
> slash.
> Leading slash results in a directory called '/' on S3.
>
> Regards,
> Peter Turcsanyi
>
> On Mon, May 16, 2022 at 12:46 PM Fill, Natalia
> wrote:
>
> > Hi Nifi Team,
> >
> > I am working on a solution to put file into S3 server. I used
> > PutS3Object and managed to put some files into a bucket, but it failed
> > to put files into specific directories on S3. No errors, but I don't
> > see the files in the bucket. I used the following format for object key:
> > /dirtag/subdirtag /${filename}. The tags do exist on S3.
> >
> > Does anyone have any suggestions how to put S3 object into specific
> > directory and not just on top level in a bucket.
> >
> > Thanks
> > Natalia
> > This e-mail (and any attachments) may contain privileged and/or
> > confidential information which may be protected by copyright or other
> > intellectual property rights. If you are not the intended recipient
> > please do not disclose, copy, distribute, disseminate or take any
> > action in reliance on it. If you have received this e-mail in error
> > please reply to the sender and then immediately delete it (including,
> any attachments).
> > Should you wish to communicate with us by e-mail we cannot guarantee
> > the security of any data outside our own computer systems or that any
> > e-mail will be virus free.
> >
> > Any information contained in this e-mail may be subject to applicable
> > terms and conditions and must not be construed as giving investment
> > advice within or outside the United Kingdom or the Republic of Ireland.
> >
> > Telephone conversations and calls via other telecommunication
> > facilities may be recorded, including to comply with our legal and/or
> > regulatory requirements and/or to monitor the quality of our service.
> > For information about how we use your personal data, including your
> > legal rights, please refer to our privacy policy at:
> >
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.legalandgeneral.com%2Finstitutional%2Fprivacy-policy%2F&data=05%7C01%7CNatalia.Fill%40lgim.com%7C6ac22dcdbd82472c4c5508da37310939%7Cd246baabcc004ed2bc4ef8a46cbc590d%7C0%7C0%7C637882980987854174%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fRb3k0FqLCtu6JlV1B77Sq1PCeQ7rOEUC8%2B5KtxkEN4%3D&reserved=0
> .
> >
> > Legal & General Investment Management Limited (Company number
> > 02091894), LGIM Real Assets (O
Re: [DISCUSS] MiNiFi C++ 0.12.0 release
I agree that it's time for a new release, thanks for RM'ing Martin. I have these two issues that I think would be nice to include in the release: 1. MINIFICPP-1828 fix InvokeHTTP Attributes to Send https://github.com/apache/nifi-minifi-cpp/pull/1331 This is a bug that is severe enough that I would prefer to wait for the fix to get merged before the release. 2. MINIFICPP-1744: Add FetchGCSObject, DeleteGCSObject, ListGCSBucket https://github.com/apache/nifi-minifi-cpp/pull/1297 This would be a nice addition to complete the GCS extension. Not necessarily required for the release, but nice to have IMO. I'll try to post a second review today or tomorrow. On Mon, 16 May 2022 at 14:57, Arpad Boda wrote: > > +1 > > On Mon, May 16, 2022 at 4:12 PM Joe Witt wrote: > > > Certainly more than enough there! Thanks Martin > > > > On Mon, May 16, 2022 at 7:06 AM Martin Zink wrote: > > > > > Hi community, > > > > > > I'd like to initiate a discussion about the next release of MiNiFi C++. > > The > > > last release was five months ago, and there have been many new features, > > > bug fixes and stability improvements committed to the development branch > > > since. (~110 commits) > > > I would be happy to take on RM duties for this release. > > > > > > New features since the 0.11.0 release: > > > - new processors: > > >* DeleteAzureBlobStorage > > >* FetchAzureBlobStorage > > >* FetchAzureDataLakeStorage > > >* ListAzureBlobStorage > > >* ListAzureDataLakeStorage > > >* PutGCSObject > > >* ProcFsMonitor > > >* PutUDP > > >* FetchFile > > >* ListFile > > >* PutSplunkHTTP > > >* QuerySplunkIndexingStatus > > > > > > - Log collection from Kubernetes > > > - improved support for Lua processors > > > - platform independent ListenSyslog > > > - property update over C2 protocol > > > > > > The core API is still not mature enough to be able to commit to it, so > > > in line with previous discussions I suggest releasing it as 0.12.0. > > > > > > Do you agree it is time for a new release? Are there any blockers that we > > > should definitely include in this release? > > > > > > Thanks, > > > Martin > > > > >
Re: [DISCUSS] MiNiFi C++ 0.12.0 release
+1 On Mon, May 16, 2022 at 4:12 PM Joe Witt wrote: > Certainly more than enough there! Thanks Martin > > On Mon, May 16, 2022 at 7:06 AM Martin Zink wrote: > > > Hi community, > > > > I'd like to initiate a discussion about the next release of MiNiFi C++. > The > > last release was five months ago, and there have been many new features, > > bug fixes and stability improvements committed to the development branch > > since. (~110 commits) > > I would be happy to take on RM duties for this release. > > > > New features since the 0.11.0 release: > > - new processors: > >* DeleteAzureBlobStorage > >* FetchAzureBlobStorage > >* FetchAzureDataLakeStorage > >* ListAzureBlobStorage > >* ListAzureDataLakeStorage > >* PutGCSObject > >* ProcFsMonitor > >* PutUDP > >* FetchFile > >* ListFile > >* PutSplunkHTTP > >* QuerySplunkIndexingStatus > > > > - Log collection from Kubernetes > > - improved support for Lua processors > > - platform independent ListenSyslog > > - property update over C2 protocol > > > > The core API is still not mature enough to be able to commit to it, so > > in line with previous discussions I suggest releasing it as 0.12.0. > > > > Do you agree it is time for a new release? Are there any blockers that we > > should definitely include in this release? > > > > Thanks, > > Martin > > >
RE: [EXTERNAL] Re: Nifi putting object to S3 directory
Hi Nifi Team,
Following from tests below I need to retrieve files from specific directories
on S3. The files are placed into dir/subdir/.
I tried various expression to specify 'filename' variable that feeds to
FetchS3Object and still get error that the key doesn't exist.
I am not sure if FetchS3Object doesn't like my directories pattern or the file
name. If I don't specify any pattern and just fetch what was listed, it works
fine.
The flow goes as follows: ListS3 (lists all the files as expected) -
UpdateAttribute (updates filename with the pattern to use) - FetchS3Object -
LogAttribute on success and on failure.
Some of my tries for filename pattern below:
*( dir/subdir/test_put_\d*_\d*\.txt).*
*( test_put_\d*_\d*\.txt).*
dir/subdir /test_put_\d*_\d*\.txt
dir/subdir /test_put_${now():format('-MM-dd')}_*
/dir/subdir /test_put_${now():format('-MM-dd')}_*
List of files on s3 server is like below:
2022-05-16 13:36:03 14 test_put_20220516_013601.txt
2022-05-16 13:36:04 14 test_put_20220516_013602.txt
Can anyone suggest how do I retrieve files in dir/subdir that start with a
particular string (e.g. test_put_) contain today's date and end with sequence
of numbers.
Thanks
Natalia
.
-Original Message-
From: Fill, Natalia
Sent: 16 May 2022 13:15
To: dev@nifi.apache.org
Subject: RE: [EXTERNAL] Re: Nifi putting object to S3 directory
Thanks Peter, removing leading slash worked and now Nifi puts file into
specified subdirectory.
This is a simple test flow to test read/write to s3: GenerateFlowFile - on
success - UpdateAttribute (filename to meaningful name) - on success -
PutS3Object - on success and on failure LogAttribute
Regards
Natalia
-Original Message-
From: Peter Turcsanyi
Sent: 16 May 2022 12:41
To: dev@nifi.apache.org
Subject: [EXTERNAL] Re: Nifi putting object to S3 directory
CAUTION: This email originated from outside of the organisation. Do not click
links or open attachments unless you recognise the sender and know the content
is safe.
Hi Natalia,
Is the FlowFile transferred to the success or the failure relationship from
PutS3Object?
In general, you need to use dirtag/subdirtag /${filename}, so no leading slash.
Leading slash results in a directory called '/' on S3.
Regards,
Peter Turcsanyi
On Mon, May 16, 2022 at 12:46 PM Fill, Natalia
wrote:
> Hi Nifi Team,
>
> I am working on a solution to put file into S3 server. I used
> PutS3Object and managed to put some files into a bucket, but it failed
> to put files into specific directories on S3. No errors, but I don't
> see the files in the bucket. I used the following format for object key:
> /dirtag/subdirtag /${filename}. The tags do exist on S3.
>
> Does anyone have any suggestions how to put S3 object into specific
> directory and not just on top level in a bucket.
>
> Thanks
> Natalia
> This e-mail (and any attachments) may contain privileged and/or
> confidential information which may be protected by copyright or other
> intellectual property rights. If you are not the intended recipient
> please do not disclose, copy, distribute, disseminate or take any
> action in reliance on it. If you have received this e-mail in error
> please reply to the sender and then immediately delete it (including, any
> attachments).
> Should you wish to communicate with us by e-mail we cannot guarantee
> the security of any data outside our own computer systems or that any
> e-mail will be virus free.
>
> Any information contained in this e-mail may be subject to applicable
> terms and conditions and must not be construed as giving investment
> advice within or outside the United Kingdom or the Republic of Ireland.
>
> Telephone conversations and calls via other telecommunication
> facilities may be recorded, including to comply with our legal and/or
> regulatory requirements and/or to monitor the quality of our service.
> For information about how we use your personal data, including your
> legal rights, please refer to our privacy policy at:
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.legalandgeneral.com%2Finstitutional%2Fprivacy-policy%2F&data=05%7C01%7CNatalia.Fill%40lgim.com%7C6ac22dcdbd82472c4c5508da37310939%7Cd246baabcc004ed2bc4ef8a46cbc590d%7C0%7C0%7C637882980987854174%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fRb3k0FqLCtu6JlV1B77Sq1PCeQ7rOEUC8%2B5KtxkEN4%3D&reserved=0.
>
> Legal & General Investment Management Limited (Company number
> 02091894), LGIM Real Assets (Operator) Limited (Company number
> 05522016), LGIM International Limited (Company number 07716001), Legal
> & General (Unit Trust Managers) Limited (Company number 01009418), GO
> ETF Solutions LLP (Company number OC329482) and LGIM Corporate
> Director Limited (Company number 07105051) are each authorised and
> regulated by the Financial Conduct Authority. All are registered in
> England & Wales with a registered office at On
Re: [DISCUSS] MiNiFi C++ 0.12.0 release
Certainly more than enough there! Thanks Martin On Mon, May 16, 2022 at 7:06 AM Martin Zink wrote: > Hi community, > > I'd like to initiate a discussion about the next release of MiNiFi C++. The > last release was five months ago, and there have been many new features, > bug fixes and stability improvements committed to the development branch > since. (~110 commits) > I would be happy to take on RM duties for this release. > > New features since the 0.11.0 release: > - new processors: >* DeleteAzureBlobStorage >* FetchAzureBlobStorage >* FetchAzureDataLakeStorage >* ListAzureBlobStorage >* ListAzureDataLakeStorage >* PutGCSObject >* ProcFsMonitor >* PutUDP >* FetchFile >* ListFile >* PutSplunkHTTP >* QuerySplunkIndexingStatus > > - Log collection from Kubernetes > - improved support for Lua processors > - platform independent ListenSyslog > - property update over C2 protocol > > The core API is still not mature enough to be able to commit to it, so > in line with previous discussions I suggest releasing it as 0.12.0. > > Do you agree it is time for a new release? Are there any blockers that we > should definitely include in this release? > > Thanks, > Martin >
[DISCUSS] MiNiFi C++ 0.12.0 release
Hi community, I'd like to initiate a discussion about the next release of MiNiFi C++. The last release was five months ago, and there have been many new features, bug fixes and stability improvements committed to the development branch since. (~110 commits) I would be happy to take on RM duties for this release. New features since the 0.11.0 release: - new processors: * DeleteAzureBlobStorage * FetchAzureBlobStorage * FetchAzureDataLakeStorage * ListAzureBlobStorage * ListAzureDataLakeStorage * PutGCSObject * ProcFsMonitor * PutUDP * FetchFile * ListFile * PutSplunkHTTP * QuerySplunkIndexingStatus - Log collection from Kubernetes - improved support for Lua processors - platform independent ListenSyslog - property update over C2 protocol The core API is still not mature enough to be able to commit to it, so in line with previous discussions I suggest releasing it as 0.12.0. Do you agree it is time for a new release? Are there any blockers that we should definitely include in this release? Thanks, Martin
RE: [EXTERNAL] Re: Nifi putting object to S3 directory
Thanks Peter, removing leading slash worked and now Nifi puts file into
specified subdirectory.
This is a simple test flow to test read/write to s3: GenerateFlowFile - on
success - UpdateAttribute (filename to meaningful name) - on success -
PutS3Object - on success and on failure LogAttribute
Regards
Natalia
-Original Message-
From: Peter Turcsanyi
Sent: 16 May 2022 12:41
To: dev@nifi.apache.org
Subject: [EXTERNAL] Re: Nifi putting object to S3 directory
CAUTION: This email originated from outside of the organisation. Do not click
links or open attachments unless you recognise the sender and know the content
is safe.
Hi Natalia,
Is the FlowFile transferred to the success or the failure relationship from
PutS3Object?
In general, you need to use dirtag/subdirtag /${filename}, so no leading slash.
Leading slash results in a directory called '/' on S3.
Regards,
Peter Turcsanyi
On Mon, May 16, 2022 at 12:46 PM Fill, Natalia
wrote:
> Hi Nifi Team,
>
> I am working on a solution to put file into S3 server. I used
> PutS3Object and managed to put some files into a bucket, but it failed
> to put files into specific directories on S3. No errors, but I don't
> see the files in the bucket. I used the following format for object key:
> /dirtag/subdirtag /${filename}. The tags do exist on S3.
>
> Does anyone have any suggestions how to put S3 object into specific
> directory and not just on top level in a bucket.
>
> Thanks
> Natalia
> This e-mail (and any attachments) may contain privileged and/or
> confidential information which may be protected by copyright or other
> intellectual property rights. If you are not the intended recipient
> please do not disclose, copy, distribute, disseminate or take any
> action in reliance on it. If you have received this e-mail in error
> please reply to the sender and then immediately delete it (including, any
> attachments).
> Should you wish to communicate with us by e-mail we cannot guarantee
> the security of any data outside our own computer systems or that any
> e-mail will be virus free.
>
> Any information contained in this e-mail may be subject to applicable
> terms and conditions and must not be construed as giving investment
> advice within or outside the United Kingdom or the Republic of Ireland.
>
> Telephone conversations and calls via other telecommunication
> facilities may be recorded, including to comply with our legal and/or
> regulatory requirements and/or to monitor the quality of our service.
> For information about how we use your personal data, including your
> legal rights, please refer to our privacy policy at:
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.legalandgeneral.com%2Finstitutional%2Fprivacy-policy%2F&data=05%7C01%7CNatalia.Fill%40lgim.com%7C6ac22dcdbd82472c4c5508da37310939%7Cd246baabcc004ed2bc4ef8a46cbc590d%7C0%7C0%7C637882980987854174%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fRb3k0FqLCtu6JlV1B77Sq1PCeQ7rOEUC8%2B5KtxkEN4%3D&reserved=0.
>
> Legal & General Investment Management Limited (Company number
> 02091894), LGIM Real Assets (Operator) Limited (Company number
> 05522016), LGIM International Limited (Company number 07716001), Legal
> & General (Unit Trust Managers) Limited (Company number 01009418), GO
> ETF Solutions LLP (Company number OC329482) and LGIM Corporate
> Director Limited (Company number 07105051) are each authorised and
> regulated by the Financial Conduct Authority. All are registered in
> England & Wales with a registered office at One Coleman Street, London, EC2R
> 5AA.
>
> Legal and General Assurance (Pensions Management) Limited (Company
> number
> 01006112) is authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential
> Regulation Authority. It is registered in England & Wales with a
> registered office at One Coleman Street, London, EC2R 5AA.
>
> Legal & General Property Limited (Registration number 02091897) is
> authorised and regulated by the Financial Conduct Authority for
> insurance mediation activities. It is registered in England & Wales
> with a registered office at One Coleman Street, London, EC2R 5AA.
>
> LGIM Managers (Europe) Limited is authorised and regulated by the
> Central Bank of Ireland (Reference No C173733). It is registered in
> the Republic of Ireland (Number 609677) with its principal business
> address at 33/34 Sir John Rogerson's Quay, Dublin 2, D02 XK09.
>
> The ultimate parent company is Legal & General Group PLC (Company
> number
> 01417162) which is registered in England & Wales and has a registered
> office at One Coleman Street, London, EC2R 5AA.
>
> __
> __
> This email has come from the internet and has been scanned for
> all viruses and potentially offensive content by Messagelabs on behalf
> of Legal & General
Re: Nifi putting object to S3 directory
Hi Natalia,
Is the FlowFile transferred to the success or the failure relationship from
PutS3Object?
In general, you need to use dirtag/subdirtag /${filename}, so no leading
slash.
Leading slash results in a directory called '/' on S3.
Regards,
Peter Turcsanyi
On Mon, May 16, 2022 at 12:46 PM Fill, Natalia
wrote:
> Hi Nifi Team,
>
> I am working on a solution to put file into S3 server. I used PutS3Object
> and managed to put some files into a bucket, but it failed to put files
> into specific directories on S3. No errors, but I don't see the files in
> the bucket. I used the following format for object key:
> /dirtag/subdirtag /${filename}. The tags do exist on S3.
>
> Does anyone have any suggestions how to put S3 object into specific
> directory and not just on top level in a bucket.
>
> Thanks
> Natalia
> This e-mail (and any attachments) may contain privileged and/or
> confidential information which may be protected by copyright or other
> intellectual property rights. If you are not the intended recipient please
> do not disclose, copy, distribute, disseminate or take any action in
> reliance on it. If you have received this e-mail in error please reply to
> the sender and then immediately delete it (including, any attachments).
> Should you wish to communicate with us by e-mail we cannot guarantee the
> security of any data outside our own computer systems or that any e-mail
> will be virus free.
>
> Any information contained in this e-mail may be subject to applicable
> terms and conditions and must not be construed as giving investment advice
> within or outside the United Kingdom or the Republic of Ireland.
>
> Telephone conversations and calls via other telecommunication facilities
> may be recorded, including to comply with our legal and/or regulatory
> requirements and/or to monitor the quality of our service. For information
> about how we use your personal data, including your legal rights, please
> refer to our privacy policy at:
> www.legalandgeneral.com/institutional/privacy-policy/.
>
> Legal & General Investment Management Limited (Company number 02091894),
> LGIM Real Assets (Operator) Limited (Company number 05522016), LGIM
> International Limited (Company number 07716001), Legal & General (Unit
> Trust Managers) Limited (Company number 01009418), GO ETF Solutions LLP
> (Company number OC329482) and LGIM Corporate Director Limited (Company
> number 07105051) are each authorised and regulated by the Financial Conduct
> Authority. All are registered in England & Wales with a registered office
> at One Coleman Street, London, EC2R 5AA.
>
> Legal and General Assurance (Pensions Management) Limited (Company number
> 01006112) is authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. It is registered in England & Wales with a registered office at
> One Coleman Street, London, EC2R 5AA.
>
> Legal & General Property Limited (Registration number 02091897) is
> authorised and regulated by the Financial Conduct Authority for insurance
> mediation activities. It is registered in England & Wales with a registered
> office at One Coleman Street, London, EC2R 5AA.
>
> LGIM Managers (Europe) Limited is authorised and regulated by the Central
> Bank of Ireland (Reference No C173733). It is registered in the Republic of
> Ireland (Number 609677) with its principal business address at 33/34 Sir
> John Rogerson's Quay, Dublin 2, D02 XK09.
>
> The ultimate parent company is Legal & General Group PLC (Company number
> 01417162) which is registered in England & Wales and has a registered
> office at One Coleman Street, London, EC2R 5AA.
>
>
> This email has come from the internet and has been scanned for all
> viruses and potentially offensive content by Messagelabs on behalf of Legal
> & General
Nifi putting object to S3 directory
Hi Nifi Team,
I am working on a solution to put file into S3 server. I used PutS3Object and
managed to put some files into a bucket, but it failed to put files into
specific directories on S3. No errors, but I don't see the files in the bucket.
I used the following format for object key:
/dirtag/subdirtag /${filename}. The tags do exist on S3.
Does anyone have any suggestions how to put S3 object into specific directory
and not just on top level in a bucket.
Thanks
Natalia
This e-mail (and any attachments) may contain privileged and/or confidential
information which may be protected by copyright or other intellectual property
rights. If you are not the intended recipient please do not disclose, copy,
distribute, disseminate or take any action in reliance on it. If you have
received this e-mail in error please reply to the sender and then immediately
delete it (including, any attachments). Should you wish to communicate with us
by e-mail we cannot guarantee the security of any data outside our own computer
systems or that any e-mail will be virus free.
Any information contained in this e-mail may be subject to applicable terms and
conditions and must not be construed as giving investment advice within or
outside the United Kingdom or the Republic of Ireland.
Telephone conversations and calls via other telecommunication facilities may be
recorded, including to comply with our legal and/or regulatory requirements
and/or to monitor the quality of our service. For information about how we use
your personal data, including your legal rights, please refer to our privacy
policy at: www.legalandgeneral.com/institutional/privacy-policy/.
Legal & General Investment Management Limited (Company number 02091894), LGIM
Real Assets (Operator) Limited (Company number 05522016), LGIM International
Limited (Company number 07716001), Legal & General (Unit Trust Managers)
Limited (Company number 01009418), GO ETF Solutions LLP (Company number
OC329482) and LGIM Corporate Director Limited (Company number 07105051) are
each authorised and regulated by the Financial Conduct Authority. All are
registered in England & Wales with a registered office at One Coleman Street,
London, EC2R 5AA.
Legal and General Assurance (Pensions Management) Limited (Company number
01006112) is authorised by the Prudential Regulation Authority and regulated by
the Financial Conduct Authority and the Prudential Regulation Authority. It is
registered in England & Wales with a registered office at One Coleman Street,
London, EC2R 5AA.
Legal & General Property Limited (Registration number 02091897) is authorised
and regulated by the Financial Conduct Authority for insurance mediation
activities. It is registered in England & Wales with a registered office at One
Coleman Street, London, EC2R 5AA.
LGIM Managers (Europe) Limited is authorised and regulated by the Central Bank
of Ireland (Reference No C173733). It is registered in the Republic of Ireland
(Number 609677) with its principal business address at 33/34 Sir John
Rogerson's Quay, Dublin 2, D02 XK09.
The ultimate parent company is Legal & General Group PLC (Company number
01417162) which is registered in England & Wales and has a registered office at
One Coleman Street, London, EC2R 5AA.
This email has come from the internet and has been scanned for all viruses
and potentially offensive content by Messagelabs on behalf of Legal & General
