Re: LLR quick clarification

[Ted Dunning]

It just means that there is an association. Causation is much more
difficult to ascertain.



On Wed, May 4, 2016 at 6:06 AM, Nikaash Puri  wrote:

> Hi,
>
> Just wanted to clarify a small doubt. On running LLR with primary
> indicator as view and secondary indicator as purchase. Say, one line of the
> cross-cooccurrence matrix looks as follows:
>
> view-purchase cross-cooccurrence matrix:
>
> I1 I2:0.9, I3:0.8, ……..
> …
>
> This, in very simple terms then means that purchasing I2 should lead to
> the recommendation of viewing I1, is that correct? Of course, ignoring the
> other indicators for now.
>
> Thank you,
> Nikaash Puri

Re: Read output of sparkrowsimilairty in scala

[Pat Ferrel]

There are several ways to do this. The design was meant to be extended by a 
trait that would do the actual read/write. Check out TDIndexedDatasetReader. 
You can create a similar trait called MySQLIndexedDatasetReader. There are 
other examples in that file for reading and writing. Also check the driver for 
how they are used. 

If you don’t like any of those you can use them to write your own code. The 
IndexedDataset includes an RDD based DRM with int keys to rows and columns, it 
also includes BiMaps called BiDictionary to translate back and forth between 
the ints and the original string row and column ids.

On May 10, 2016, at 2:43 AM, Rohit Jain  wrote:

Hello,
I am writing scala code to pull data from db and run row-similarity
analysis. After running spark-rowsimilarity I want to read data returned by
function directly write it back to mysql db. But I don;t know how to read
the data from indexeddataset returned by
val data = SimilarityAnalysis.rowSimilarityIDS(myIDs)
In debugger it shows datatype as Indexeddataset which contains
(matrix,rowIDs,columnIds).

Thanks.--
Thanks & Regards,

*Rohit Jain*
Web developer | Consultant
Mob +91 8097283931