2. Register Tables

Our catalog is created and we can start registering tables in it.

---

Step 1: Select Data

We'll work with the following three source tables in the M5_STORE_SALES_AMOUNT schema:

Table	Description
SALES	Daily total sales amount (revenue) per store, with an IANA timezone column.
CALENDAR	Per-state daily calendar with event names and unified SNAP eligibility flag.
STORE_STATE	Mapping from store to US state.

---

Step 2: Locate Your Data

From the menu, go to the Explore section and access the Source Tables.

Go to the DEMO_DATASETS database, and select the M5_STORE_SALES_AMOUNT schema.

---

Step 3: Explore Tables

Select the tables to get familiar with the data.

Click to generate a summary for each table. Click to read the full summary.

Click one table to view its columns and preview its values.

---

Step 4: Understand Table Types

For accurate feature derivation, FeatureByte needs to recognize the roles of different tables.

Each table should be assigned a specific type based on its structure and purpose:

• SALES --> Time Series table.

  Why Time Series Table?

  The table provides daily sales records per store, forming a regular time series. Each row represents one store's revenue for one day.

• CALENDAR --> Calendar table.

  Why Calendar Table?

  The table contains per-state daily information (events and SNAP flags) that enriches the time series with external context. Using a Calendar Table allows FeatureByte to automatically derive features from calendar attributes at the forecast point.

• STORE_STATE --> Dimension table.

  Why Dimension Table?

  The table provides a static mapping from store to state, used to link the store entity to the state entity for calendar lookups.

---

Step 5: Register the SALES table as a Time Series Table

1. Select the SALES table.

2. Click on to start registration.

3. Click on to get assistance:

   

   You should confirm or update the following fields:

   • Table type

     • Set Table Type to Time Series Table

   • Key and Timestamp columns

     • Reference Datetime Column: date
     • Reference Timezone Column: timezone
     • Reference Timezone Column Type: timezone
     • Series ID Column: store_id
     • Time Interval: DAY
     • Record Creation Timestamp: record_creation_date

   

   ---

4. Establish a Default Feature Job Setting as a CRON job: daily at 2:30 AM with a America/Los Angeles timezone.

   

   ---

5. Complete registration by clicking .

Timezone Column

The SALES table includes a timezone column with IANA timezone names (e.g. America/Los_Angeles for California stores, America/Chicago for Texas and Wisconsin stores). This tells FeatureByte that the date column is in local time and each store's timezone is specified per row.

---

Step 6: Register the CALENDAR table as a Calendar Table

1. Select the CALENDAR table.

   

   ---

2. Click on .

3. Click on to get assistance:

   You should confirm or update the following fields:

   • Table type

     • Set Table Type to Calendar Table

   • Key and Timestamp columns

     • Calendar Datetime Column: date
     • Series ID Column: state_id

   

   ---

4. Complete registration by clicking .

Why state_id as Series ID?

The calendar is expanded to per-state rows, with a unified snap column that reflects whether SNAP purchases were allowed in that specific state on each day. Using state_id as the series ID allows FeatureByte to join the correct state-level calendar information to each store.

---

Step 7: Register the STORE_STATE table as a Dimension Table

1. Select the STORE_STATE table.

   

   ---

2. Click on .

3. Click on to get assistance:

   You should confirm or update the following fields:

   • Table type

     • Set Table Type to Dimension Table

   • Key columns

     • Dimension ID Column: store_id

   

   ---

4. Complete registration by clicking .

---

Step 8: Review Registered Tables

Verify the registration by checking the Table Catalog under the 'Explore' section.