Yes you need 2 queries but a better schema design. I think you might be trying to optimize where it actually will not give you any gain except few lines of less code. Can you give an example of what you are trying to do?
Other question why not store in within the same row? On Sat, Oct 29, 2011 at 10:22 AM, Aditya Narayan <ady...@gmail.com> wrote: > ..so that I can retrieve them through a single query. > > For reading cols from two CFs you need two queries, right ? > > > > > On Sat, Oct 29, 2011 at 9:53 PM, Mohit Anchlia <mohitanch...@gmail.com> > wrote: >> >> Why not use 2 CFs? >> >> On Fri, Oct 28, 2011 at 9:42 PM, Aditya Narayan <ady...@gmail.com> wrote: >> > I need to keep the data of some entities in a single CF but split in two >> > rows for each entity. One row contains an overview information for the >> > entity & another row contains detailed information about entity. I am >> > wanting to keep both rows in single CF so they may be retrieved in a >> > single >> > query when required together. >> > >> > Now the problem I am facing is that I want to cache only first type of >> > rows(ie, the overview containing rows) & avoid second type rows(that >> > contains large data) from getting into cache. >> > >> > Is there a way I can manipulate such filtering of cache entering rows >> > from a >> > single CF? >> > >> > >> > > >
