ThoughtSpot Best Practices - Alias or Role Playing Dimensions
What is the best way to model Alias or Role-Playing Dimensions in ThoughtSpot. For example I have an airport fact table with Origin and Destination.
I also have a lookup table for Airport:
Can I use 1 lookup table for airport or do I need to bring in the lookup table for airport twice (one to join fact to original_airport_id, one to join fact to destination_airport_id).
You can use one table for airport and have multiple joins corresponding to origin/destination. When searching, the system will prompt the user to pick the desired path. If users are working against worksheets, the worksheet can have join paths resolved. Worksheets can have the same column brought in multiple times - each with a different join path.