PySpark apply same StringIndexer on multiple columns
up vote
3
down vote
favorite
I have the following Dataframe
+--------------+---------------+
| SrcAddr| DstAddr|
+--------------+---------------+
| 192.168.100.5| 192.168.220.16|
| 192.168.100.5| 192.168.220.15|
|192.168.220.15| 192.168.100.5|
|192.168.220.16| 192.168.100.5|
| 192.168.100.5| 192.168.220.15|
|192.168.220.16| 192.168.100.5|
| 192.168.220.9| 192.168.100.5|
| 192.168.100.5| 192.168.220.9|
| 192.168.220.9| 192.168.100.5|
+--------------+---------------+
containing source and destination address IPs.
I want to transform them in numerical index by means of StringIndexer, but I want to learn a common mapping between the columns.
Unfortunately StringIndexer does not provide such a rich interface in PySpark. Thus I found a workaround, but I wanted to know if there is a better way to do it.
What I have done is the following:
First, I compute the union between the two columns
src_addr_df = df.select(["SrcAddr"]).withColumnRenamed("SrcAddr", "Addr")
dst_addr_df = df.select(["DstAddr"]).withColumnRenamed("DstAddr", "Addr")
all_addr_df = src_addr_df.union(dst_addr_df)
Then, I learned a common StringIndexer over the newly created DataFrame:
addrIndexer = StringIndexer(inputCol="Addr", outputCol="AddrIdx")
addrModel = addrIndexer.fit(all_addr_df)
Finally, I used the learned model to transform the original dataframe. This, is the tricky part because I need to rename the columns quite often to obtain the desired results:
df = addrModel.transform(df.withColumnRenamed("SrcAddr", "Addr")).withColumnRenamed("Addr", "SrcAddr").withColumnRenamed("AddrIdx", "SrcAddrIdx")
df = addrModel.transform(df.withColumnRenamed("DstAddr", "Addr")).withColumnRenamed("Addr", "DstAddr").withColumnRenamed("AddrIdx", "DstAddrIdx")
Thus, I'm wandering if there is the possibility to rather change the InputCol value of the StringIndexer, which would create a much readable code
Best regards,
Sandro
python dataframe pyspark
add a comment |
up vote
3
down vote
favorite
I have the following Dataframe
+--------------+---------------+
| SrcAddr| DstAddr|
+--------------+---------------+
| 192.168.100.5| 192.168.220.16|
| 192.168.100.5| 192.168.220.15|
|192.168.220.15| 192.168.100.5|
|192.168.220.16| 192.168.100.5|
| 192.168.100.5| 192.168.220.15|
|192.168.220.16| 192.168.100.5|
| 192.168.220.9| 192.168.100.5|
| 192.168.100.5| 192.168.220.9|
| 192.168.220.9| 192.168.100.5|
+--------------+---------------+
containing source and destination address IPs.
I want to transform them in numerical index by means of StringIndexer, but I want to learn a common mapping between the columns.
Unfortunately StringIndexer does not provide such a rich interface in PySpark. Thus I found a workaround, but I wanted to know if there is a better way to do it.
What I have done is the following:
First, I compute the union between the two columns
src_addr_df = df.select(["SrcAddr"]).withColumnRenamed("SrcAddr", "Addr")
dst_addr_df = df.select(["DstAddr"]).withColumnRenamed("DstAddr", "Addr")
all_addr_df = src_addr_df.union(dst_addr_df)
Then, I learned a common StringIndexer over the newly created DataFrame:
addrIndexer = StringIndexer(inputCol="Addr", outputCol="AddrIdx")
addrModel = addrIndexer.fit(all_addr_df)
Finally, I used the learned model to transform the original dataframe. This, is the tricky part because I need to rename the columns quite often to obtain the desired results:
df = addrModel.transform(df.withColumnRenamed("SrcAddr", "Addr")).withColumnRenamed("Addr", "SrcAddr").withColumnRenamed("AddrIdx", "SrcAddrIdx")
df = addrModel.transform(df.withColumnRenamed("DstAddr", "Addr")).withColumnRenamed("Addr", "DstAddr").withColumnRenamed("AddrIdx", "DstAddrIdx")
Thus, I'm wandering if there is the possibility to rather change the InputCol value of the StringIndexer, which would create a much readable code
Best regards,
Sandro
python dataframe pyspark
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I have the following Dataframe
+--------------+---------------+
| SrcAddr| DstAddr|
+--------------+---------------+
| 192.168.100.5| 192.168.220.16|
| 192.168.100.5| 192.168.220.15|
|192.168.220.15| 192.168.100.5|
|192.168.220.16| 192.168.100.5|
| 192.168.100.5| 192.168.220.15|
|192.168.220.16| 192.168.100.5|
| 192.168.220.9| 192.168.100.5|
| 192.168.100.5| 192.168.220.9|
| 192.168.220.9| 192.168.100.5|
+--------------+---------------+
containing source and destination address IPs.
I want to transform them in numerical index by means of StringIndexer, but I want to learn a common mapping between the columns.
Unfortunately StringIndexer does not provide such a rich interface in PySpark. Thus I found a workaround, but I wanted to know if there is a better way to do it.
What I have done is the following:
First, I compute the union between the two columns
src_addr_df = df.select(["SrcAddr"]).withColumnRenamed("SrcAddr", "Addr")
dst_addr_df = df.select(["DstAddr"]).withColumnRenamed("DstAddr", "Addr")
all_addr_df = src_addr_df.union(dst_addr_df)
Then, I learned a common StringIndexer over the newly created DataFrame:
addrIndexer = StringIndexer(inputCol="Addr", outputCol="AddrIdx")
addrModel = addrIndexer.fit(all_addr_df)
Finally, I used the learned model to transform the original dataframe. This, is the tricky part because I need to rename the columns quite often to obtain the desired results:
df = addrModel.transform(df.withColumnRenamed("SrcAddr", "Addr")).withColumnRenamed("Addr", "SrcAddr").withColumnRenamed("AddrIdx", "SrcAddrIdx")
df = addrModel.transform(df.withColumnRenamed("DstAddr", "Addr")).withColumnRenamed("Addr", "DstAddr").withColumnRenamed("AddrIdx", "DstAddrIdx")
Thus, I'm wandering if there is the possibility to rather change the InputCol value of the StringIndexer, which would create a much readable code
Best regards,
Sandro
python dataframe pyspark
I have the following Dataframe
+--------------+---------------+
| SrcAddr| DstAddr|
+--------------+---------------+
| 192.168.100.5| 192.168.220.16|
| 192.168.100.5| 192.168.220.15|
|192.168.220.15| 192.168.100.5|
|192.168.220.16| 192.168.100.5|
| 192.168.100.5| 192.168.220.15|
|192.168.220.16| 192.168.100.5|
| 192.168.220.9| 192.168.100.5|
| 192.168.100.5| 192.168.220.9|
| 192.168.220.9| 192.168.100.5|
+--------------+---------------+
containing source and destination address IPs.
I want to transform them in numerical index by means of StringIndexer, but I want to learn a common mapping between the columns.
Unfortunately StringIndexer does not provide such a rich interface in PySpark. Thus I found a workaround, but I wanted to know if there is a better way to do it.
What I have done is the following:
First, I compute the union between the two columns
src_addr_df = df.select(["SrcAddr"]).withColumnRenamed("SrcAddr", "Addr")
dst_addr_df = df.select(["DstAddr"]).withColumnRenamed("DstAddr", "Addr")
all_addr_df = src_addr_df.union(dst_addr_df)
Then, I learned a common StringIndexer over the newly created DataFrame:
addrIndexer = StringIndexer(inputCol="Addr", outputCol="AddrIdx")
addrModel = addrIndexer.fit(all_addr_df)
Finally, I used the learned model to transform the original dataframe. This, is the tricky part because I need to rename the columns quite often to obtain the desired results:
df = addrModel.transform(df.withColumnRenamed("SrcAddr", "Addr")).withColumnRenamed("Addr", "SrcAddr").withColumnRenamed("AddrIdx", "SrcAddrIdx")
df = addrModel.transform(df.withColumnRenamed("DstAddr", "Addr")).withColumnRenamed("Addr", "DstAddr").withColumnRenamed("AddrIdx", "DstAddrIdx")
Thus, I'm wandering if there is the possibility to rather change the InputCol value of the StringIndexer, which would create a much readable code
Best regards,
Sandro
python dataframe pyspark
python dataframe pyspark
edited Nov 22 at 8:43
JoSSte
83311331
83311331
asked Nov 22 at 7:52
Sandro Cavallari
164
164
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53426165%2fpyspark-apply-same-stringindexer-on-multiple-columns%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown