Yes, that's correct (though you forgot to use the code tag). You haven't described the shape of table1. I'll make a guess though. Assuming that table1 has TRIGGER_ID as the foreign key, and an INSERT_DATE column to make the row unique, then you'd want do to two things:
1) Change your many-to-one mapping in table2 to include property-ref="TriggerID", so that it doesn't try to join on your ID (which will have two columns, so won't join to table2 which only has one column available, TRIGGER_ID).
2) Set up your table1 mapping like this:
Code:
<class name="table1" ...>
<composite-id>
<key-many-to-one name="Table2" class="Table2" column="TRIGGER_ID"/>
<key-property name="InsertDate" type="date" column="INSERT_DATE"/>
...
</composite-id>
...
</class>
Obviously, this applies only if FK/Date make up your unique id for table1. You haven't said what makes up the unique id: perhaps this solution isn't appropriate.
The are other ways of achieving the same thing. I would prefer to use a <list> mapping in table2, containing a component: that way you don't need a separate mapping for table1. You'll have to show me the shape of table1 and table2 before I can determine if that's a better solution for you.