Big Data Loading Chapter 2 - PROC Lasr TAGS

[odesh]

Hello,

I do not quite understand why we  need the concept of tags with PROC LASR. In the example given, could be not simply name the 2 tables to be unique:

1. mylaser.bank_prd 

2. mylaser.bank_dev   

or something similar rather than having to define a new concept of  "tags".  I must be missing something ..

Regards.

Odesh

[Cynthia_sas · Accepted solution]

Hi:

  This is from one of the instructors:

"Very typically when customers are testing new features in their environment they maintain both a development and a production area. They are duplicates of each other. So that means the table names would all be duplicate. The customer would not want to change the table names because the whole purpose is to see what would happen to the exact same table in the development area.

There are many more examples where a client might have two tables with the same name in two different locations. Tags are how the LASR server works around the limitations of the two level library.table name issues in the in-memory environment."

Hope this clarifies that sometimes you can't change the table names and therefore, need a way to deal with duplicate names on the LASR server.

Cynthia