Out of Resources means that your Xcalar Cluster doesn’t have enough memory to complete the operation. The most common source is a team not knowing about some of our recommended best practices for modeling:
* Locking important Temporary Tables
* Then, dropping unlocked Temporary Tables
* Separating projects into Workbooks.
* Duplicating your Workbook before dropping tables if you are unsure as-to whether you should lock or drop a particular virtual table.
* Deactivating your Workbook to provide teammates with off-peak opportunities for high-memory utilization activities.
Every column tweak you mentioned creates a new virtual table, whose metadata is stored in memory. As a result, many smaller operations will add up to significant memory usage over time, especially across your entire team.
You could also be running into a less common source of memory concern. If you are already following the best practices, would you include a sample screenshot of the schemas or anonymized data for the two tables you are attempting to join? That should give us the context to ask you the right questions to move you forward! A join is memory intensive, but doesn’t generally cause “Out of Resources” error messages. With some more information about the challenge you are facing, I’m sure we can figure this out.