This was noticed in T351197#9447809.
output-sql.js assumed that `actor.client` is not `undefined`:
```lang=js
function generateInsertActorQueries( actor ) {
const actorObj = {
actor_data: {
ip: actor.ip,
org: actor.organization,
client_count: actor.client.count || 0,
types: actor.client.types ?
getActorTypes( actor.client.types ) : actorTypes.UNKNOWN,
conc_city:
actor.client.concentration && actor.client.concentration.city ? actor.client.concentration.city : '',
conc_state:
actor.client.concentration && actor.client.concentration.state ? actor.client.concentration.state : '',
conc_country:
actor.client.concentration && actor.client.concentration.country ? actor.client.concentration.country : '',
countries: actor.client.countries || 0,
location_country: actor.location.country || '',
risks: actor.risks ? getActorRisks( actor.risks ) : riskTypes.UNKNOWN
},
...
```
If it is, an error is thrown.
We haven't actually encountered this problem in real data, but according to Spur's documentation, `actor.client` is not "required": https://docs.spur.us/#/data-types?id=ip-context-object