Index wal edits should be written to the wal associated to index region instead main region wal

[chrajeshbabu]

  Long time = indexWALEdit.getKeyValues().get(0).getTimestamp();
  ctx.getEnvironment()
      .getWAL()
      .appendNoSync(indexRegion.getRegionInfo(), Bytes.toBytes(indexTableName), indexWALEdit,
        logKey.getClusterId(), time, indexRegion.getTableDesc());

[chrajeshbabu]

Presently there is no problem. later if we support multi-WAL feature it will help.
Its minor only..

[anoopsjohn]

How I would like to see this in future when multi WAL comes is
Multi WAL will have a pluggable way of deciding the region group associated with one WAL
We will have an impl which will make sure both index region and actual region go to one group
Again core should support writing WAL data for more than one region together in one HLogEntry